I've written an app which compiles quotes for my company.  Currently it runs
locally on the client machines.  I'd like to link the client DB's to a
server DB, updating any information that's not there.  A few key
requirements:

1.  Quote Numbers are incremted by 100, i.e. 199,299,399 etc.  Each Quote#
must be distinct
2.  Some client machines are laptops that are regularily taken into the
field, and quotes are often made on site.  The server DB must be able to
handle this

I'm relatively new to Access DB programming ( < 2 months).  Can anybody
point me in the right direction regarding how to set up this system?  I'd
REALLY appreciate any help any Access gurus could give me #:->

TIA

parry

--
----------------------------------------------------------------------------
-----------------
"What you don't understand is that I've crippled more
 people than polio."

http://www.*-*-*.com/ ~pmalm

There is no magic. A possible solution is to live with "temporary" number
and "certified". While disconnected, give temporary number, like 498, 598,
698, ...and after replication (it may requires many synchronisation),
"certify" those numbers (6099, 6199, 6299, ... ). Since the "certified"
number is required only when you speak with the "exterior" you are not
really oblige to cascade update 498 to 6099, as example, that may simplify
the synchronisation. Access has replication built-in, you may take a look at
"Access 97  Developer's Handbook", at Sybex (take care, there was a similar
title at MS Press), by Litwin, Getz and Gilbert. Take note that autonumbers
become random number once replication is engaged.

Hoping it may help,
Vanderghast, Access MVP.