FMTouch 1.42 Problem with Auto Entered Numbers

[macsmarts]

My main database uses an auto-entered number as a unique field and primary key. The FMtouch database loses track of the next number in the sequence and ends up duplicating a number already in use. Syncing the FMtouch database with it's parent fixes the problem, but any related records created (say, in a portal) are linked to the duplicated number and are now attached to another record.

[macsmarts]

So the question is, how can a new record be created on a remote FMtouch database - with a key that will not be a duplicate of a key generated in the past (because FMtouch seems to have lost track of the next number).

What method besides sequential numbering will insure a unique key for records generated on FMtouch?

[macsmarts]

Correction, the related records do get linked correctly once synced but still....