I'm creating an ER Diagram for a legacy database here. I have a serious of tables that are different versions of the same data. One is a 'Raw' copy of the current data, i.e. what the exact data as it was received and input into the system. Another is the live data after the raw data has been validated and corrected. There are also a series of older versions of the data that predate the current system. Basically one table per year from 1975 to 1990.
These tables are not a child-parent relationship. They are basically the same data with some variations of fields as time goes on. Is there an ER standard to express this type of relationship? Do I just use a normal connector? The part that is confusion me mostly is that the concept of a 'primary' and 'foreign' keys does not really apply here, does it? These tables basically all have the same keys that are not dependent on each other. I'm currently using MS Visio to create this diagram and I'm a bit worried about it creating unnecessary and possible incorrect 'relationship' implication such as marking fields as a foreign key if that is not what they really are? I generally find that the farther one strays from the 'norm'; the more difficult|obscure MS products can be about allowing one to do what one wants. Did I explain this clearly? Thank You Ian ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;192386516;25150098;k Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:305246 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
