O
Offace
Hi News Group,
I'm currently constructing a single user database using Access 2003 for data
storage only, i.e. only data tables and queries are in the database
(interface and business rules deleveloped using C#). I have read, not only
from this news group, problems that can occur if values assigned in a
Primary Key ID field are, populated using AutoNumber assignment type, adding
1 to the maximum value of the ID field, and the use of a control table
containing the 'next id' for the tables fields requiring it. Not trying to
be pedantic but now rather confused, what is the best way for a database I
have as such to assign long integer values to a primary key? Given that the
database is single user and no replication required. I have seen GUID
mentioned here and there, is this option worth considering? How is it
implemented? Is there any method that will attain an ID value that holds
credibility?
Any help is appreciated. Thanks in advance.
Regards,
Offace.
I'm currently constructing a single user database using Access 2003 for data
storage only, i.e. only data tables and queries are in the database
(interface and business rules deleveloped using C#). I have read, not only
from this news group, problems that can occur if values assigned in a
Primary Key ID field are, populated using AutoNumber assignment type, adding
1 to the maximum value of the ID field, and the use of a control table
containing the 'next id' for the tables fields requiring it. Not trying to
be pedantic but now rather confused, what is the best way for a database I
have as such to assign long integer values to a primary key? Given that the
database is single user and no replication required. I have seen GUID
mentioned here and there, is this option worth considering? How is it
implemented? Is there any method that will attain an ID value that holds
credibility?
Any help is appreciated. Thanks in advance.
Regards,
Offace.