security question

  • Thread starter Thread starter SuzyQ
  • Start date Start date
S

SuzyQ

I have a database that I set up as secure. What I want is to create a new
database, but use the same security file that is being used on the current
database. My goal with this new database is simple. I just want to be able
to open it, have it check the other database's version and create a copy of
the that database using the version number as part of the file name, and then
open the that database and close itself. That way I will always have a
current copy of the database prior to making any changes to it.
 
On Wed, 28 Oct 2009 14:07:02 -0700, SuzyQ

You might want to look at Tony Toews updater tool at
autofeupdater.com.
Another option is msbackup.exe already on your computer.

-Tom.
Microsoft Access MVP
 
I have already set up my updater program (several years ago) That's not what
I was asking about. I want to make a copy of MY development version prior to
making changes to MY version - not the production version. I just need to
know how to attach an already existing security file to a newly created mdb.
 
The reason I went into the explanation in my OP was hopefully to clarify
things not make them muddier. I have my MDB that I make changes to - when
I'm ready I publish it as a MDE to the network. When the user logs into
their local version it checks to see if there is a newer version, and if
there is, it updates it. That is NOT what I need help with.

What I want is to make a copy of MY MDB prior to making any changes in the
development environment. I've been doing that manually, but want an
automated way of doing it. I ran into trouble when it tried to check the
version of my development MDB because the security file was not attached to
my copy version table. The reason I want to check is so that my backups are
numbered. IE. My MDB is named PublicWorks.MDB I want to copy for it backup
as...

Copy of PublicWorks_1_1j (1).mdb
Copy of PublicWorks_1_1j (2).mdb etc...

So that the next time I open my copyVersion.mdb it will check the version,
see that it is 1.1j, check the backups already used and assign the next
backup the name Copy of PublicWorks_1_1j (3).mdb, then open PublicWorks.MDB
and close copyVersion.mdb

That way as I make modifications, but before I publish, I can go back if I
need to start over or whatever.
 
I solved it. I just needed to put the /w switch in the settings of the
shortcut. Major brain fart! - I actually answered this question for someone
else about two months ago. I don't know what I was thinking! :)
 
Back
Top