Forum Discussion
#Deleted issue with GUID
Working with GUIDs is one way to achieve your goal, but it is a more complex method than relying on Integers set to Identity to autogenerate new values for a Primary Key.
You need to ensure that your method for adding new records includes creating a new GUID for the PK in each table before trying to save that record. As Arnel said, using GUIDs is not a common approach, so finding an example of that might require a more extensive search.
Also, you must be sure that Access recognizes this Primary Key field as the Primary Key field when linking those tables. When a table has an integer with Identity Specification set, Access identifies it as the PK, but in this case, it might not do so. You'll have to be sure you designate it when creating the links so that Access can use it in forms and subforms, etc.
Rarely anybody uses GUID (unless you know what you are doing and its purpose).
Thank you for your reply,
My goal is a off-line application. For example, 10 off-line apps will consolidate on the same database, depending on when they are able to connect to internet. The idea is not to have the same PK for differents records from different apps. Would you have a suggestion ?
