Synchronising Between laptop and Desktop

[Douglas J. Steele]

What you're looking for is called Replication.

You don't mention what version of Access you're using.

For Jet 3.5x (Access 97), look at
Replication White Paper
http://support.microsoft.com/?id=164553
Replication FAQ
http://support.microsoft.com/?id=182886 -

For Jet 4.0 (Access 2000 and 2002), look at
Replication White Paper
http://support.microsoft.com/?id=190766
Replication FAQ
http://support.microsoft.com/?id=282977

Also see
http://www.trigeminal.com excellent replication site
http://support.microsoft.com/support/access/content/repl/replication.asp

 

[Raistlin]

OK, here's another question that I'm hoping somebody can help me with.

The end users of the database that I'm currently working on will be using a
desktop machine and a laptop machine.

The Laptop will be used "on site" to input customer details and test
results, the desktop will be used for printing reports and certificates
based on the test results.
There is also the possibility that customer details and results will be
added using the desktop machine.

The worry that I have is that it is conceivable that two identical customer
ID's will be generated on the two different machines (the customer ID is an
autonumber field in the main customer details table and is also the primary
key for that table).

I'm guessing that the easiest way to transfer data between the two is by
exporting from one in CSV format and then importing to the other. Then I
need to reverse the process and do things the other way to make sure that
both machines have the same data in them.

Can anybody see any problems here, or offer any advice on the best way to do
things?

If you need more info, or if I'm not being overly clear (my apologies, it is
very late!), please ask.

Thanks in advance,

Raist.

 

[Raistlin]

What you're looking for is called Replication.

You don't mention what version of Access you're using.

<SNIP>

Sorry about that, I'm using Access 2000 (came with Office 200 Pro).

Thanks for the URL's, I've had a quick browse but I think I need to spend
more time reading through the info there.

On the surface it looks like the replication needs to be an instantaneous
2-way process (via LAN,WAN or dial-up connection), I'm planning on using a
floppy (I know, I know!). Is this likely to be possible do you think?

I suppose if only new records are transferred then it should be ok, if the
whole database is transferred each time then I'm going to be in trouble.

I'm trying to create a (suedo) application that is going to be fairly
sizeable when done. Unfortunately I don't have the benefit of the
developers ed. of Access (don't know whether that would help or not) and
I've not been using Access for very long.
What I don't want to do is spend a lot more time on this (probably measuring
the working time in terms of months rather than weeks) if it's not going to
be a viable option to synchronise the two machines.

Thanks for your help so far, I'll take a good look at the info in those
URL's and see what I can work out.

Regards,

Raist.

 

[Douglas J. Steele]

Thanks for the URL's, I've had a quick browse but I think I need to spend
more time reading through the info there.

Yup, it's a fairly complicated proposition.

On the surface it looks like the replication needs to be an instantaneous
2-way process (via LAN,WAN or dial-up connection), I'm planning on using a
floppy (I know, I know!). Is this likely to be possible do you think?

If you read http://www.trigeminal.com/usenet/usenet009.asp, you'll see that
using a floppy is definitely not recommended.

I suppose if only new records are transferred then it should be ok, if the
whole database is transferred each time then I'm going to be in trouble.

I'm trying to create a (suedo) application that is going to be fairly
sizeable when done. Unfortunately I don't have the benefit of the
developers ed. of Access (don't know whether that would help or not) and
I've not been using Access for very long.
What I don't want to do is spend a lot more time on this (probably measuring
the working time in terms of months rather than weeks) if it's not going to
be a viable option to synchronise the two machines.

To be honest, I've got no experience with replication, but I believe you do
need the Developer edition to get the license for the components required
for replication.

It is possible to build your own home-grown version of replication (I know I
did it in Access 2.0), but it's definitely not a simple matter.