:( I know there has to be a simple, elegant solution for this, but I seem to have brain-lock. I have a simple database with three tables. The first and second table is related with a one-to-many relationship. I currently have an id created by using Auto-Enter Serial Number field options.

Serial numbers work great unless you need to later work on a copy of the database to make changes and then import the data into the modified file. Obviously when you do the import a new set of serial numbers are generated - not good. What is the CORRECT method for generating serial numbers that won't recalculate/redefine with import into a duplicate database.

you could use the number equivalent to the time stamp and concatenate the record id. that should be relevantly a good general use UID

check this out

http://fmforums.com/forum/showtopic.php?tid/100135

Edited August 13, 200718 yr by Guest

Cool idea

Whoa, you do not generate new serial numbers on import. Turn off that option when you import and just bring your records in with their original serial numbers. Remember to sort by serial number field and find the maximum value and set the counter to one number greater than that maximum.

All this can be scripted, and done with a click of a button. Use the Set Next Serial number script step.

Or, work on the system while it's down or make small changes while it's in use and avoid the import/export routine altogether.

You can also try 360Works ScriptMaster Plugin it is Java incased in a plugin it has a function to create UID's

http://www.fmforums.com/forum/showtopic.php?tid/189032/

The ideas so far are good. I've got a nasty calculation that would create a unique identifier if I didn't want to use the serial number. I don't want to get locked into having to set the import to avoid auto-updates...I may need that feature.

I want to create an id (some calculation) and then never let it change again. I wish I could always do updates on site or via VPN, but it's not always an option...