Up Liftting to Access 2010

[luis baptista]

I'm convinced that following the conventional unique | autonumbered key fields produces the best relational integrity and thats what I'm persuing
But how to achieve this when the tables of the previous aplication do support autonumbered key fields, without busting the relational integrity of that previous aplication data base ??
Any clues other than developing an aplication just migrate data from the old to the new data base ?

[alansidman]

Create new tables with an autonumber field, and all the other fields from the old db. Run an append query to append all the old data to the new table.

[luis baptista]

Thanks a lot. I'l try just that. But was I clear about the fact that there I'm dealing with several old aplication tables with no autonumbered key fields ?

[alansidman]

Yes. You were clear. In an append query, if you set your new table with the autonumber, it should populate properly. BTW, I would make a backup of my db before I started any of the updates.

[June7]

You will also have to run UPDATE queries to update new foreign key field in dependent tables with the new autonumber primary key. Once everything is properly related on the new fields, the old fk fields can be removed.

[alansidman]

@June. Good point. I had forgotten about the FK aspect. A little bit of tunnel vision took over and was thinking only of the PK.

Alan