I haven't heard of issues with using an autosequence number as a primary key (as long as it isn't expected to be related to the data itself).

My question was directed at the difference between using the Database.Execut e method vs. Recordset.AddNe w. AddNew allows the code to retrieve fields (namely autogenerated ones) from the new record immediately but when working with tables with upwards of 60 columns it's not as easily coded...

Hi all! I'm looking for a 'best practices' solution - or at least a more elegant one to my problem.

My application tracks changes made to existing records. So I need to:
1. Begin a transaction
2. Copy the original record to the tracking table.
3. Fetch the autosequence number (key) of the newly inserted record.
4. Use the key of the tracking record to update a related table with linked records (e.g....

I need to add modification tracking to an existing database. It's effectively the same as the std. Orders/Order Details model so I'll use that for an example.

If a user makes a change to an existing order I need to be able to deactivate the original record and generate a new Order record. The same goes for any Order Details that are also changed. The idea is that users should be able to view what an Order looked like at a particular...