Many users

  • Thread starter Thread starter Casey
  • Start date Start date
C

Casey

What you want to do is first make a copy of your
database and leave your original intact. Next using your
new copy (name it something else than the original), use
the Tools menu option and create a replica of your new
copy, having it placed in the network location that you
want it to reside. This is safe to do since you are using
a copy of and not your original. The replica will be the
one that resides on the network, and the copy that you
used to create that replica will be the design master.
Now any changes you make to the design master, will be
reflected in your copy on the network as long as you have
rights to that area of where the replica is residing.
What will happen is you will make make changes to the
master, and when you want those changes to reflect in your
replica on the network, just use the "synchronize"
replicas feature from your tools menu option. Also, you
might want to make the file on the network non deletable
in its properties to assure noone deletes it on you.

If you ever have problems with your master file just
make a copy of what you had placed on the network, open it
up, go to the tools menu option and choose recover design
master, and just answer that you cannot find your original
design master and access will turn the file into the new
design master, then make a new replica of it at the
network location for your users.

If you ever get sick of using a replica, just create
a new blank database, and import all of the pieces from
the replica into it, and you will have a new non-replica
file.

This I know will definitely work for you, and is not
complicated to do.

I hope I have helped.

Casey
 
[snip]
If you ever get sick of using a replica, just create
a new blank database, and import all of the pieces from
the replica into it, and you will have a new non-replica
file.

This I know will definitely work for you, and is not
complicated to do.

I hope I have helped.

Casey
Click to expand...
I have never messed with replication, so I wouldn't really be able to
comment on how that works.

That said, at the risk of being inflammatory, I'm not sure why the
original poster (OP) is so extremely adamently against splitting the
database. Everything I've read as well as my own experience clearly
makes the case for it almost everytime in situations like this. It
leaves the designer secure in the knowledge that their data is not
being "cross-contaminated" when they make design changes. It's
fundamentally sound.

Sounds like the original poster (OP) just needs to get over himself
and go with it, or deal with the consequences.

LRH
 
Larry R Harrison Jr said:
"Casey" <[email protected]> wrote in message
[snip]
If you ever get sick of using a replica, just create
a new blank database, and import all of the pieces from
the replica into it, and you will have a new non-replica
file.

This I know will definitely work for you, and is not
complicated to do.

I hope I have helped.

Casey
Click to expand...
I have never messed with replication, so I wouldn't really be able to
comment on how that works.
Click to expand...

I fail to see how replication will help in this situation.

Replication is intended for tables only, not for any other objects.
 
Back
Top