J
JMF
I realize this subject has been discussed in various forms other times, but
I need to make another pass through it.
The last time I saw it was when a poster wrote that he had makes of cars
(Ford, Toyota, etc.) and wanted another field to have the specific model.
That field, of course, depends on the make of the car.
Another situation is for example, time management for a number of projects,
where each project has a set of tasks. So if you want to have two fields,
for project and task, the task will depend on the project.
Since I'm relatively new to Access, it doesn't seem like this can be handled
without "special treatment." That is, you can't just use the standard
editing facilities, but have to begin using things like "on update" or other
techniques that have been mentioned, including some VB programming possibly.
In fact, it seems like it's a relational database thing, the difficulty of
working with fields that depend on each other in the same table. But I
haven't even found a reasonable solution when trying to separate things out
into different tables.
But of course, as a newcomer I may be completely wrong, and would be happy
to get insights from experts! So, does anybody have any insights or
direction to point me in to understand better the topic of "when one field
depends on another"?
Thanks,
John
I need to make another pass through it.
The last time I saw it was when a poster wrote that he had makes of cars
(Ford, Toyota, etc.) and wanted another field to have the specific model.
That field, of course, depends on the make of the car.
Another situation is for example, time management for a number of projects,
where each project has a set of tasks. So if you want to have two fields,
for project and task, the task will depend on the project.
Since I'm relatively new to Access, it doesn't seem like this can be handled
without "special treatment." That is, you can't just use the standard
editing facilities, but have to begin using things like "on update" or other
techniques that have been mentioned, including some VB programming possibly.
In fact, it seems like it's a relational database thing, the difficulty of
working with fields that depend on each other in the same table. But I
haven't even found a reasonable solution when trying to separate things out
into different tables.
But of course, as a newcomer I may be completely wrong, and would be happy
to get insights from experts! So, does anybody have any insights or
direction to point me in to understand better the topic of "when one field
depends on another"?
Thanks,
John