sophie_ross
New member
- Local time
- Today, 19:39
- Joined
- Jun 5, 2003
- Messages
- 5
Does anyone know the procedure MSA uses to order records when assigning the autonumber field?
Oh good lord, where to start. I've merged 6 separate non-relational (poorly designed) access databases into one, got rid of duplicate records and built a new structure for the data using a relational database with 11 tables. My problem is that I need to populate my new structure with the data from the old table and it just ain't happening!
The problem lies with the primary key - I want to retain the original primary key so I can keep track of the records while I sort out what data goes into which table. BUT then I can't switch that primary key back to Autonumber of course. So, I created a new field for autonumber but when it assigns the number I can't work out how it indexes the records since the consecutive numbering doesn't match the old primary key! This would be easy to manage if it applied the same rule to each table I update so the records all retained the same key even though it didn't match the original but it doesn't!
Basically how do I split up these 2500 records into a dozen tables whilst retaining their primary keys so the records still relate to each other but new keys will be assigned after...
Does that make any sense?!
Oh good lord, where to start. I've merged 6 separate non-relational (poorly designed) access databases into one, got rid of duplicate records and built a new structure for the data using a relational database with 11 tables. My problem is that I need to populate my new structure with the data from the old table and it just ain't happening!
The problem lies with the primary key - I want to retain the original primary key so I can keep track of the records while I sort out what data goes into which table. BUT then I can't switch that primary key back to Autonumber of course. So, I created a new field for autonumber but when it assigns the number I can't work out how it indexes the records since the consecutive numbering doesn't match the old primary key! This would be easy to manage if it applied the same rule to each table I update so the records all retained the same key even though it didn't match the original but it doesn't!
Basically how do I split up these 2500 records into a dozen tables whilst retaining their primary keys so the records still relate to each other but new keys will be assigned after...
Does that make any sense?!