I am working on a document/part/item control application using an Access database to hold my data. One of the operations of the application is that there is a table that contains a record for each document/part/item (these have slashes because in reality they are the same thing). To modify any document/part/item a change request is used, another table. The change request table has a primary key that is the CR# which is assigned to the document/part/item being changed (called a revision) as a foreign key.
I feel that in my document table I have no need to create a new record for a revised document, since all of the information about the revision is contained in the change request record, so there exists only one record for each document. The document record then gets a new foreign key value each time the document is revised.
My question, is this considered a kosher way to handle a database and if not why?
Database usage in VB
Post a Reply
|Oldest Newest Rating|
One of the first products to provide a graphical environment and a paint metaphor for developing user interfaces.
|Bucky Roberts Administrator|