Multi-Valued Fields and Revision History

[Mickey]

So, I have been reading that it is impossible to create a "revision history"
table for a set of records that use multi-valued fields. But I am a believer
in loop-holes, so I think there has to be another way to create a "revision
history" table for my records without using an append query (which can't be
run if using multi-valued fields). I was wondering if there is some way for
me to make a subdatasheet in my original table that just adds on the record
changes to the subdatasheet? If anyone has any ideas to help me create this
"revision history" table without taking out my multi-valued fields, please
let me know. Thank you!

Each record in my main field has a primary key (autonumbered) telling the
project's project number. The multi-valued fields in the table include
Clients (that each project affects), Themes (that each project addresses),
etc.

 

[Roger Carlson]

Your database can only be improved by taking out the multi-value fields.
Not the answer you want to hear, but it's the only one I'll give.
Multi-value fields are great for small, quick-and-dirty databases. But when
you get to the point when you want to create a Revision History, you need to
build it right.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L

 

[Mickey]

:/ I had a feeling. Thanks for the reply, though!