Replication and Duplication

I am currently in the process of trying to create an Access Database Application. The database will be located on a local network and multiple laptops. In thinking over the table structure I found a duplication problem that will cause issues when synchronizing.

For most of my primary keys I can use a replciation id and they will be unique. However, when I get into creating the orders table I know I will have problems with the Invoice Number. I don't want to use a replication id for an invoice number and the invoice number will always need to be unique. I won't have a problem with the database on the LAN, I will see it on the laptops when they sync.

Does anyone have any suggestions on how to get around this. Any help you could provide would be appreciated.

Thank you,
Kevin McBrearty

Kevin,

You do not say why you do not want to use the replication ID for the invoice
number. Is there a specific reason?

However the invoice number must be unique, which will mean that you will
have to create a unique number for each invoice. You will need to identify
something that is unique that you can use as part of the number. If all
salesmen have a unique staff ID, you could use that for example so that even
if you are incrementing a number for each new order, including the staff ID
in the number will make all numbers unique (e.g. StaffID 1378, invoices
13781,13782 etc). Alternatively, you could use the number for their initials
followed by an incrementing number. So an invoice raised by you would be
1113 followed by the incrementing number with the 11 and 13 representing the
K and M
I'm sure you can think of others as well.

Dave
"Kevin McBrearty" wrote in
message ...
I am currently in the process of trying to create an Access Database
Application. The database will be located on a local network and multiple
laptops. In thinking over the table structure I found a duplication problem
that will cause issues when synchronizing.

For most of my primary keys I can use a replciation id and they will be
unique. However, when I get into creating the orders table I know I will
have problems with the Invoice Number. I don't want to use a replication id
for an invoice number and the invoice number will always need to be unique.
I won't have a problem with the database on the LAN, I will see it on the
laptops when they sync.

Does anyone have any suggestions on how to get around this. Any help you
could provide would be appreciated.

Thank you,
Kevin McBrearty

"Dave Jones" wrote in
:

So an invoice raised by you would be
1113 followed by the incrementing number with the 11 and 13
representing the K and M


Bearing in mind, of course, that the StaffIDCode would be kept in a
separate field from the InvoiceSerialNumber; and then the two could be
printed and displayed as a single string if required.

Tim F