Re: >> Synchronize switch?

• Previous message: Graeme Richardson: "Re: MSDE replication experience"
• In reply to: Jonathan Parminter: ">> Synchronize switch?"
• Messages sorted by: [ date ] [ thread ]

Date: Sat, 22 Jan 2005 15:21:13 GMT

Sounds like something is amiss in your setup. Replication is designed
for DATA only (tables) and should not be used for Access OBJECTS
(forms, queries, reports). In other words, it is intended for the
backend database in a split frontend/backend design. If you are using
replication to distribute "application" design changes to your users,
then you should switch your design to a split frontend/backend
architecture.

See http://www.granite.ab.ca/access/splitapp/index.htm for some good
information.

Then, if your database is split, all your users should be connected to
a single backend on the network and you will not require Replication.

On Wed, 19 Jan 2005 16:09:04 -0800, Jonathan Parminter <Jonathan
Parminter@discussions.microsoft.com> wrote:

>Hi, users have a copy of the master database in their personal network drive.
>So I am unable to update their copy to match the current version. I can have
>a table in their copy that has a version number. On opening, their database
>can compare their version with the master database.
>
>But is there already some internal switch that I can check to determine
>whether the user must sychronize their replica (and then automate this...)?
>
>If 'yes' how do I check to determine that the replica needs to sychronize as
>this may only need to happen infrequently?
>
>Any ideas or suggestions appreciated :-)
>
>Thanks
>Jonathan

**********************
jackmacMACdonald@telusTELUS.net
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security

• Previous message: Graeme Richardson: "Re: MSDE replication experience"
• In reply to: Jonathan Parminter: ">> Synchronize switch?"
• Messages sorted by: [ date ] [ thread ]