In message , Trini
Gal writes
Hello,

I've read a lot of the threads referencing Primary Key and I need a little
help. I'm creating a database for my company to track changes to channels.
This database will be accessed in different regions throughout the company
(possibly sometimes at the same time). I need to figure out how to create a
Primary Key for one of my tables. I've figure out how to use the DMax
function to increment #s, but if two users try to enter a new record at the
same exact time, one of them won't be able to save that record because the
one before got the #. I know this because its happened before.

If your database is going to be accessed by lots of people
simultaneously then it's worth considering whether Access is the right
tool for the job. Depending on the usage pattern you may want to
consider using a client-server database like SQL Server which can wrap
multiple updates into a transaction.

If all you want is a unique ID then an autonumber field will do the job.
Don't your tables have natural keys?


--
Bernard Peek