Backup/Mirror of Split database in multi-user env.

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Stan Schnuerer - 12 Apr 2004 20:31 GMT

I have a split database that I am solely updating.

I have users doing only reading of the data through forms, queries, and linked tables. However, at this time the shared file locations on the network I have to work with don't offer any "rogue" user protection, ie. deleting of the files

Therefore, I want to be the only one working with the original copy of the database and have the users see only a "mirror copy" (updated immediately whenever the original "master copy" is). Replicas look promising but I rely on autonumber being sequential, so that is not preferred

I thought of automating all updating functions to run twice, once for the "master" and once for the "mirror" copy. I am somewhat accomplished with VBA so this is my first choice right now, despite the tax on storage space. Also, later I hear we will have better document control measures in place so this all may be moot

Anyone have suggestions/similar experiences

Reply to this Message

Douglas J. Steele - 12 Apr 2004 21:11 GMT

I haven't got a good answer for you, but I wanted to comment on your
statement "I rely on autonumber being sequential".

That's not a particularly good thing to do. Autonumbers exist for one
purpose only: to provide a (practically guaranteed) unique value that can be
used as a primary key. You should make no further assumptions about them.
They can (and usually will) have gaps in numbering. It's rare to even show
the value of the autonumber field to your users.

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(No private e-mails, please)

> I have a split database that I am solely updating.
>
> I have users doing only reading of the data through forms, queries, and linked tables. However, at this time the shared file locations on the

network I have to work with don't offer any "rogue" user protection, ie.
deleting of the files.

> Therefore, I want to be the only one working with the original copy of the database and have the users see only a "mirror copy" (updated immediately

whenever the original "master copy" is). Replicas look promising but I rely
on autonumber being sequential, so that is not preferred.

> I thought of automating all updating functions to run twice, once for the "master" and once for the "mirror" copy. I am somewhat accomplished with

VBA so this is my first choice right now, despite the tax on storage space.
Also, later I hear we will have better document control measures in place so
this all may be moot.

> Anyone have suggestions/similar experiences.

Reply to this Message