Synchronizing Tables between local and server databases

[Brian]

First, let me apologize for this being so long, but I
wanted to give a good explanation so whomever reads this
can understand what I am trying to do.

I have a rather large Access database (front end and back
end) shared among 10 users. One of my users wants to be
able to use this database at home. The idea would be that
he would be able to use it at work and then take his
laptop home and use the database there as well. He wants
access to any data added at work by anyone. And any data
he adds at home must then be accessible to everyone at
work upon his return.

The data that must be shared right now is comprised of
73200 records in 19 different tables across three
different access .mdb files. Each table has a [LastDate]
field in which the date and time the record was last
updated is recorded.

The first thing we did was increase our DSL speed to 3MB
download/768k upload. Unfortunately, this was not fast
enough to support running Access. (He has a 2-way cable
modem at his house.) I then wrote VBA code to look at and
compare the [LastDate] field between his local copy and
the server. Unfortunately, when comparing 73000+ records,
this took about 20 minutes...way too long.

Hence my question to anyone who has cared to read this
far...How do I go about doing this? Is there software I
can buy to do a record-by-record comparison? Is my logic
all wrong in the VBA program? Is this just plain old not
possible to do quickly (less than a minute or so)?

Any info/help would be most appreciated!
Thanks!
Brian

 

[Michel Walsh]

Hi,


Try using a software "capturing" a PC over a remote link. The PC on the
local network works as usual, and only what is displayed on the monitor is
to be carried over the slow connection. So, if the PC on the LAN has to pump
some records, that will be as performing as the other PC on the LAN. The
remote is basically just concerned by the display, NOT by getting the binary
data from the database, so even a slow connection won't be much noticeable.
The problem is that it requires two PC (one remote and one on the local
LAN).



Hoping it may help,
Vanderghast, Access MVP