Problem with Replicating Database

[michaelak117]

I have converted my 2007 DB to 2003 to take advantage of the security features and have applied some. Once I have gone to replicate the database in order to make it available for more users and have sycronization capabilities I have run into a problem. Once I create a Design Master Copy and then create a replica I am unable to open the replica. The error message says it cannot be open because I do not have the permissions and must contact the administrator or the designer. That would be me, yet I still cannot open it. I noticed the same issue when I converted my database to a secure on using the USER level security Wizard, but it created a shortcut that would allow me to open it.

I need to find out how whats causing this problem and how to open this replica database. Is anyone familiar with these security features and can tell me how to enable myself to open the replica? Thanks

 

[HiTechCoach]

I have converted my 2007 DB to 2003 to take advantage of the security features and have applied some. Once I have gone to replicate the database in order to make it available for more users and have sycronization capabilities I have run into a problem. Once I create a Design Master Copy and then create a replica I am unable to open the replica. The error message says it cannot be open because I do not have the permissions and must contact the administrator or the designer. That would be me, yet I still cannot open it. I noticed the same issue when I converted my database to a secure on using the USER level security Wizard, but it created a shortcut that would allow me to open it.

I need to find out how whats causing this problem and how to open this replica database. Is anyone familiar with these security features and can tell me how to enable myself to open the replica? Thanks

If you are using the built in security, then you will need to always use a shortcut to open the database that includes the path the the correct MDW.

I normally place the work group file (MDW) in the same folder as the back end and the front end will be local on each work station.

Will have remote users that are not on the same network? Is the why you need replication?

I have found that you only replicate the back end. This means that you must split the app into a front end and back end. Since the back end is the only thing that is replicated, you normally you will not need to open a replica. You open a normal Front end with a short cut using the correct work group (MDW).

The design master should not be used in normally production. I keep it tucked away in a safe place. It only needs to be used to modify the table design. in the back ends at the remote locations.

Both the built in security and replication are a lot to get your head around to get correctly implemented. I would highly recommend that you do a lot of testing before rolling anything out to the users.

 

[michaelak117]

I am a little confused about splitting the db. When you split dont you have a back end with only tables? Then you recommend distributing the front end to the workstations. If im understanding correctly, are you recommending an alternative because splitting the database would leave no point in replicating as replicating would be useful only if you have all db features (forms, macros, queries,etc) to work elsewhere and then syncronize with the Design Master. To answer your question, yes users may be working remote. I appreciate your response and advise, as I am surely taking my time on this project.

 

[boblarson]

Replication should only be used on pure jet objects (tables/queries). You do NOT, I repeat, do NOT use replication on forms, reports, macros, and modules - so yes you replicate BACKENDS ONLY.

See here for more about replication:
http://dfenton.com/DFA/Replication/index.php?title=Main_Page

 

[Rabbie]

I am a little confused about splitting the db. When you split dont you have a back end with only tables? Then you recommend distributing the front end to the workstations. If im understanding correctly, are you recommending an alternative because splitting the database would leave no point in replicating as replicating would be useful only if you have all db features (forms, macros, queries,etc) to work elsewhere and then syncronize with the Design Master. To answer your question, yes users may be working remote. I appreciate your response and advise, as I am surely taking my time on this project.

From my own experience I have a DB split FE/BE Each user has their own copy of the FE lnked to the BE. One user needs to be able to use the DB when away from base so I have replicated the BE. The Design Master is kept in a safe location on the server and most users are linked to a copy on the server while the other user has their own copy on their laptop. These are synchronised regularly on return to base.

 

[michaelak117]

Users are linked to the design master aka the BE and your mobile employee keeps a replica on his laptop? I think what your describing would be sufficient for my needs. I am unclear and unlearned on linking the FE with BE though. Could you explain this further. How do I link users to the BE. The mobile user is syncronized back when he returns correct, not requiring any links?

 

[Rabbie]

Users are linked to the design master aka the BE and your mobile employee keeps a replica on his laptop? I think what your describing would be sufficient for my needs. I am unclear and unlearned on linking the FE with BE though. Could you explain this further. How do I link users to the BE. The mobile user is syncronized back when he returns correct, not requiring any links?

Firstly as advised by David Fenton the design master is NOT used in production work. For production work I use a replica on the server that is synchonised with the other replica on the laptop. Synchronisation with the design Master are done less frequently
For advise on splitting your DB try searching these forums. There are some very good links which should help you

 

[boblarson]

An Example:

1. You have a split database (Frontend/Backend).

2. You Replicate the backend to the user's laptop

3. If you use the same file location on all laptops (example: C:\Program Files\MyDatabase\my_database_be.mdb) for where the replica will go, then

4. You link one copy of the frontend to the replicated backend in C:\Program Files\MyDatabase\my_database_be.mdb and then you give a copy of that frontend to each user. And, because you've stored the replicated backend on their machines, in the exact same file location - no relinking is necessary.

5. Each users uses a copy of the frontend that has been linked to the replica on their machine.

6. When users are back connected to the network, they can synch their backends.

Does that help?

 

[michaelak117]

That pretty much does it. Thanks alot for laying that out for me, greatly appreciated. Easier than I had originally thought.