thats what i thought...
i guess all i can do is make a nice form, and adivse everyone else that if they choose not to use it then nothing will be there to keep them from making mistakes
thanks for the info
others will have access to the tables
its not my choice and i cant do much about it
so basically the only way to enforce nested column options is via a Form?
it seems there is some limited data checking in datasheet view, since i can specify 'Limit to List' for the column lookup
but it looks...
thanks,
but all those examples use Forms to enforce the dependancy
the people who use this are going to have direct access to the data tables themselves
so the cascading restriction needs to be enforced on the datasheet view itself
is that possible?
I see how the cascading combo box solution...
Hi,
I'm new to Access, but I've used a lot of SQL
I dont really know where to start on how to do this...
I have items in a table that are organized by Category and SubCategory
where the SubCategories allowed should be dependant on the Category
how do I enforce such a dependance?
I've figured...