Recent content by odingalt

Ok good example (Thank you). So the Manufacturer field with a datatype of "short text" would work great, and we could put manufacturer's in a separate table tblManufacturers if we wished, and use a combobox to restrict data entry to predefined manufacturers. Let's say we tracked...

Is it normal to store all the data as datatype "short text"? That seems to be the result in boblarson's example. Unless we create multiple tblPreferenceDetails, one for each datatype?

Try post #7 instead? (boblarson attached the .mdb to that thread for posterity, it supercedes the old broken URL link)

On an aside. When it's time to create a new asset, would it be best practice to have a "Create new asset" button (VBA script) that pre-populates the tblPreferenceDetail with all possible preferences, and then fills in records in the tblPreferenceDetail with a dummy record for each possible...

I am using boblarson's sample database posted back up on page 1 of this thread. (It seems redundant to attach it here so I will just refer back to that post). If I understand what is being said at the beginning of this thread, the idea is to put all assets into a single table (rather than...

Thanks for the insightful thread. Let's just say I have an equipment/asset tracking database, but because of the way the tables are structured (different table for each equipment type), it's become difficult to manage and certain features are much more difficult to implement (such as tracking...