Synchronizing through code locks up database for editing

I have about 5 laptops, all with a front and back end database on their
hard drives. The central server has the main back end database as well
as the deisgn master on it.

When users login to the front end database on their harddrives, they
have two options: login remotely (don't synchronize) and login from
office (synchronize). The problem is that when they login from the
office and synchronize, parts of the database "lock up". The two parts
that lock up are:

1. Local front-end tables (unlinked to the back-end) that aren't
replicable cease to work properly. These are temporary tables that are
generated frequently and on the fly from procedures within the
front-end. The data WILL build into the table correcly, but it won't
requery in forms without multiple requery attempts. When users login
without synchronizing, everything works fine. When they login and
synchronize, these tables/requeries of their data start malfunctioning.

2. I can't make design changes after synchronizing, I get an error
message that I don't have exclusive use of the database - even though I
do my design changes at night when no one else is logged in.

The data does synchronize OK, and I don't get any error messages. I
just get these 2 "lock-out" malfunctions after synchronizing.

Here is my synchronization code:

Public Function synch()
Dim LocalDataSet As Database
Set LocalDataSet = OpenDatabase("C:\Database\Bsysdata.mdb")
On Error GoTo err_synch
LocalDataSet.Synchronize "\\HPPavilion\database\Bsysdata.mdb"
LocalDataSet.Close
MsgBox "Local Server Detected..." & vbCrLf & vbCrLf & _
"Data Synchronized Successfully", vbOKOnly
Exit Function

err_synch:
MsgBox "Local server not detected..." & vbCrLf & vbCrLf & _
"Please synchronize when you are connected to the network",
vbOKOnly
End Function


Any help is GREATLY appreciated!

.

Relevant Pages

  • Re: Synchronizing through code locks up database for editing
    ... When users login to the front end database on their harddrives, ... login from office (synchronize). ... Are you not waiting until the synch finishes before allowing the ...
    (microsoft.public.access.replication)
  • Re: Primary keys/rep IDs and other basic (not for me!) things
    ... I have a database that will ... can have a replica that can ... want to synchronize design changes in the front end -- you just want ... only real complication is relinking to the back end, ...
    (microsoft.public.access.replication)
  • Pocket Access sync problems with pc replica
    ... Each PDA will have a replica of the database on it. ... The order of which tables synchronize first etc cannot ... I can write code to get around the problems Active Sync has, ...
    (microsoft.public.access.replication)
  • Pocket Access sync problems
    ... Each PDA will have a replica of the database on it. ... The order of which tables synchronize first etc cannot ... I can write code to get around the problems Active Sync has, ...
    (microsoft.public.access.setupconfig)
  • Developing and syncing MS Access on with Pocket Access
    ... Each PDA will have a replica of the database on it. ... The order of which tables synchronize first etc cannot ... I can write code to get around the problems Active Sync has, ...
    (microsoft.public.access.devtoolkits)