Importing Best Practices

[Stuart Taylor]

I have a script that imports any number of records & there related records into a solution.

Lets say Contact Table Records & Related Address Table Records & Tel Numbers stored in separate tables.

The data file being populated is hosted on fm server & shared by a large number of users all capable of creating records. Any user can import data & add records.

Anyone got any thoughts on the best way to do deal with attributing the correct serial numbers that the records will receive when they are added to the main data file and how i should pass that to the new related records before they are imported as this new serial will be there ID field?

Any best practices here?

I am also thinking that the process needs to account for records being created by other users on the network whilst the process is taking place or even others doing similar imports.

Any shared experiences would be useful.

Best

Stuart

[mr_vodka]

I usually work with a temp table. Import into the temp table, import into the main parent table. Assign the record ID to a utility foreign key field in temp table, import into the sub child tables with now foreign key.

[Stuart Taylor]

Thanks Mr V

So import with import ID & pass back via a calculation?

best

Stuart