Just solved this problem last night and thought I'd share it with you. I't happened to me several times, so maybe someone out there has had a similar experience.You've just imported a stack of tables from another system (mainframe, DB4, whatever) into MSAccess. The data SHOULD be relationally coherent, but when you start setting up the relationships with Access, they all fail because there are references in foreign tables to primary keys that don't exist. For example, there are orders for customers that have been deleted. You have dozens of tables and tens of thousands of records and the boss wants something cool for tomorrow morning.
|
