How do you mean? Usually when creating a replica MSAccess strongly recommends that you create a backup. It will do it for you, creating a file called whateverthedatabaseiscalled.bak. You can rename this file .mbd
Ok, I am going to keep the replication the way it is for now. But I am having problems with networking now that it is replicated. When I place a copy of it on an end users workstation it cannot find the back-end. When I go through the Link Table Manager it says, "You cannot make design changes to this Replica".
How do I place this onto co-workers workstations and mantain the network setings?
Did the replication affect my split database? In other words, should I have split the database after replication?
From what little I have read on the subject, replication only applies to data. This would mean that the stages are:
1. Split database;
2. Replicate back-end only.
You can have as many front-ends as is reasonable, without replicating.
There is no link. It is just something I have done, to see. It really is very, very tedious. Maybe someone does have a link, though. Are you sure you can't remember where you put the backup? :-(
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.