Splitting a Replicated DB

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

yerbmeld - 25 May 2006 02:50 GMT

I am working with a replicated database that was created by someone
else. The database is not split at this time and we've been
experiencing erratic behavior from some of the forms. I can split the
database easy enough and I can deploy the new front end to the current
users. My questions are:

1. Should I just link to the local back end replica and synch when
closing the database? Or, should I check if the network replica hub is
available and if it is, link to it as the back end?

2. How do I determine if the user is connected to the network to synch
with the replica hub?

3. How do I deploy the local front end db to new users and create their
local replica back end db?

Replication is new to me and I appreciate any guidance you can provide.

Darrell

Reply to this Message

David W. Fenton - 25 May 2006 13:58 GMT

> I am working with a replicated database that was created by
> someone else. The database is not split at this time and we've
[quoted text clipped - 5 lines]
> closing the database? Or, should I check if the network replica
> hub is available and if it is, link to it as the back end?

This is up to you. I think it's preferable to share the edited
replica whenever possible, so I'd use the LAN replica when
connected. But it depends entirely on your setup. It may just be
easier for the user who is only occasionally working on the LAN to
just always edit the local replica and synch when the LAN replica is
available.

> 2. How do I determine if the user is connected to the network to
> synch with the replica hub?

Use the Dir() command to see if files on the server are accessible.
However, you have to realize that this can sometimes give inaccurate
results (indicating a live connection when there is none) because of
the way Windows networking caches information about network
resources. Thus, you need to have appropriate error handling in your
synchronization routine and then you could trap for the error that
is raised when the partner replica is inaccessible and return an
appropriate error message to the user.

> 3. How do I deploy the local front end db to new users and create
> their local replica back end db?

If you keep the same replica and just remove the forms/reports/etc.,
a regular synch should update the data. For distributing the front
end, just zip up and email the MDB file to them and tell them were
to extract it to.

> Replication is new to me and I appreciate any guidance you can
> provide.

The question of distribution of front end updates is not a
replication question at all, of course. It's one that is relevant
all split databases (which should be 99.99% of all Access
applications).

Signature

David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

Reply to this Message