Compact on close or not?

[boblarson]

For example instead of adding another field to the customer table to record a new aspect of the customer, have a related table that stores many different aspects of the customer each identified by a field with a key to the name of the aspect being recorded.

These aspects are displayed in a subform in either continuous or datasheet mode so there is no need to alter the form when a new aspect is added.

Great idea Galaxiom. And I have a sample on my website which demonstrates this concept. (just in case anyone wanted an example)

 

[spikepl]

#20 Some developers' nightmares, and some others' bread and butter
I agree with you that shifting the goalposts tends to be interesting, but again, in this instance it was clear from the outset that that was the way it was going to be.

Thanks for the suggestion on adding stuff - I was already considering automating changes in existing tables, but your way seems much better. In a month's time or so, the req's should be settled enough to decide what is what, and then I will pobably refactor the entire code anyway.

#21 Thanks for the sample