Synchronize MS Access database

[dev guy]

hi

I have MS Access databases on machines at physically different locations.
One of the machine would act as the master server. whereas the other
machines will act as clients. The schema of the MS Access database on all
the machines (including the server) will be identicle.

The data from database on client machines will need to be synchronized with
the database on the server machine. There will be some data insertion and
updation on the server machine which will need to be synched with the client
machine.

The client and the server machines are not on LAN/WAN/Internet. There is no
physical or internet connectivity between these. So the syncronization
mechanism has to be offline form

How this can be achieved?
What are various options to achieve this?
What about the primary keys (which may be autonumber on say clinet)

Is there any middleware available to do so, automatically? I know this is
possible using IIS, but we are not in a position to maintain IIS on the
server location.

Thanks in advance.

 

[Jeff Dillon]

No connectivity? Then you'll have to burn a CD at the client. Or USB Memory
Chip, or similar.

Then look under Replication under the Tools menu in Access

Jeff

 

[Tim Ferguson]

The client and the server machines are not on LAN/WAN/Internet. There
is no physical or internet connectivity between these. So the
syncronization mechanism has to be offline form

Have you looked at database replication? Seems this is what it was invented
for.


HTH


Tim F

 

[Paul Clement]

¤ hi
¤
¤ I have MS Access databases on machines at physically different locations.
¤ One of the machine would act as the master server. whereas the other
¤ machines will act as clients. The schema of the MS Access database on all
¤ the machines (including the server) will be identicle.
¤
¤ The data from database on client machines will need to be synchronized with
¤ the database on the server machine. There will be some data insertion and
¤ updation on the server machine which will need to be synched with the client
¤ machine.
¤
¤ The client and the server machines are not on LAN/WAN/Internet. There is no
¤ physical or internet connectivity between these. So the syncronization
¤ mechanism has to be offline form
¤
¤ How this can be achieved?
¤ What are various options to achieve this?
¤ What about the primary keys (which may be autonumber on say clinet)
¤
¤ Is there any middleware available to do so, automatically? I know this is
¤ possible using IIS, but we are not in a position to maintain IIS on the
¤ server location.
¤
¤ Thanks in advance.

You will need to take a look at the solution Tim mentioned:

Database Replication in Microsoft Jet 4.0
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnacc2k/html/dbrepjet.asp


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)

 

[Lynn Trapp]

Have you looked at database replication? Seems this is what it was
invented

for.

It would be ideal, except that Access replication requires some kind of
connection between the design master and the replicas.

 

[Jeff Dillon]

So what are you expecting? Connectivity through thin air?

"I need gas from the gas station, but I can't get there"

"So get a can, and start walking"

You might try praying...I've heard this works in mysterious ways.

Jeff

 

[Lynn Trapp]

So what are you expecting? Connectivity through thin air?
Hmmmmmmmm...that was my point exactly. Replication will NOT work if there is
no connectivity.

 

[Tim Ferguson]

Hmmmmmmmm...that was my point exactly. Replication will NOT work if
there is no connectivity.

There's always the SneakerNet, which is what I was brought up with! I
assume the OP was at least one step further on than paper forms...

Tim F

 

[Lynn Trapp]

There's always the SneakerNet, which is what I was brought up with! I

assume the OP was at least one step further on than paper forms...

Good old SneakerNet. I have to use that with one of my clients that does not
have email.