To my limited knowledge this is not really possible. Though I guess anything is possible with enough coding.
I must wonder why this would be needed though. This can be done in a form easily enough and a Table is not really meant to be a data entry form.
most of the changes would go through the form side..
but when the user does queries to change the data, then they would change it at the table level.
I am with Darasen, having your users work at Table level can be very disastrous. You should develop Forms and Queries. The Queries will feed the exact data to your forms for the users to input and manipulate. The ending result will still be stored in the table, unless it is a calculated field. So I would advise against using Tables as a source of Data Entry.
Now, that being said, check back later on today. I found a sample of just what you are looking for. But even then, it is not at the Table, but in a form which has 2 ComboBoxes. You make a selection in the first box and the data for the second is changed to pull from the now changed options are in the first. Like this, in the beginning both ComboBoxes are blank. In the first you are to choose a State. Once you do that, the second ComboBox will only show you the Cities within the selected state. Sound like what you need???
Heading to be now it's almost 3a.m. but will try to find it and post it on here for you.
Remember from a safety and logical point of view, do not use a Table for data entry purposes. You can create a Form to do that and Design it for DatasheetView, which resembles the look of a Table. My reason for this, Tables are very volatile and allowing someone access directly to it, with them not knowing it or it being intentional, they can accidentally delete a Field/Record, wipe out data when moving to that field, etc....you get the picture. Just passing along what was taught from the pros.
have a nice day
keep a look out for later today, unless someone else resolves it before I get back.
yes i knw..the disasters of working at table level are enormous..since they aren't imposed restrictions..but our adminstrators have sufficient knowledge with the DB and + the use for which i'm using this for is not a complicated situation. Its a simple cascading solution with two combo boxes;
i have done it before a lot of times on forms, with 2 or 3 combo boxes...where they 'cascade' of each other..that aint hard
BUT, aside from all the generous warnings you guys have given, i just need a straight answer if this is indeed possible at THE TABLE level.
Once again, i dont mean to be brusque, i just need to know if its possible.
Well, for my final conclusion on this matter is that can't be done at table level. I asked around and nobody I talked to knew of how you program easily if at all at Table level. Might have to find you a real programming heavy hitter to make the table work that way. With Forms as you know you can go behind the scenes to do fancy work, but not known of a way to control Tables that way. I was told that Tables are just holding tanks for the raw data. So from me, NOT AN EXPERT, it can't be done.
Not really sure why if it can be done easily in a form it just HAS to be done in a Table. Isn't the end result to just get it done? Not being a smarty or anything just trying to get a better insight myself. After all, I come here not only to try to help, BUT to learn as well....so that is why I always ask.
Hey, if you find a way I would appreciate you posting the solution here for all to see, then we will all be the wiser.