Does filemaker generate a RecordID (retrievable by the get(RecordID) funtion) that is unique to the Entire database, or only the current table?

Cheers,

~Genx

It generates a unique RecordID for each table. But that doesn't mean it is safe to use in place of regular unique IDs because if data is imported/exported, the RecordIDs could be the same. They numerically jump by ever-increasing increments as the size of the table increases. :wink2:

Righto, so i'm not missing out on much, yay.

Any potentially interesting uses for it at all?

Cheers,

~Genx

"... if data is imported/exported, the RecordIDs could be the same..."

I'm not sure that the recids suddenly become non-unique, I believe that the problem is the recids *change* when the nrecords are exported/deleted/imported (say when importing into a clone) which means relationships that relied on the recids will break.

It depends on whether you import the records with the IDs or without. If you do import the original IDs, subsequent new records may auto-enter duplicates. If, during import, you auto-enter fresh ones instead, then your relationships will break.