Michael Brosdorf
michael.broesdorf at web.de
Fri Jul 16 10:01:38 CDT 2004
Hi Nancy, 1. Create a new database with the same tables as your production db's 2. Do not use autonumbering for the pk columns - make them long integers instead 3. Import all data from database A, multiplying the pk and fk values by 10, adding 1 4. Import all data from database A, multiplying the pk an fk values by 10, adding 2 5. Convert the pk-columns to autonumber fields This way, all pk-values from db A will have a 1 at the end, all pk-values from db B will have a 2, keeping all related data together. Michael -----Ursprungliche Nachricht----- Von: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]Im Auftrag von Nancy Lytle Gesendet: Freitag, 16. Juli 2004 16:45 An: AccessD at databaseadvisors.com Betreff: [AccessD] Take a formatted number and turn it into a "real" number I just got handed a database of about 30 tables (about half are lookups), there are about 10 tables with varying relationships that are fairly well defined. There is an identical - but unconnected - version of the database at our West Coast location. I have now been tasked with merging the two. At first I thought it would be easy because it appeared they were using two different numbers schemes for the PK's turns out they just formatted them to "look different" but the matching tables use the same Autonumber - start from 1 - field type. So now I have to figure out a way to merge them without messing up all the relationships. Does anyone have any ideas? Both databases are still being used so I have to come up with a way I can do it with the least down time possible. TIA, Nancy -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com