B
BonnieW via AccessMonster.com
Hello!
I'm trying to figure out whether it's possible to set up certain controls
(textboxes and comboboxes) to "lock in" certain inputs when the user checks a
box. (this sounds weird, I know, but we had a third-party app, no longer
supported, which did this).
So, for instance, we have the controls Date, Point, Species, and Behavior.
If someone went to Point 1 on 1/1/01, and saw five different species, each
doing different things, then we would want the user to be able to input the
point name and the date, indicate that they were to remain contstant til the
user changed them, then go and enter in species and behaivor information.
However, it's also likely that the user would have only one species at any
given point, or want to enter the data in reverse order (say, if they saw an
American Bittern at 8 different points, each with the same behavior, on one
or two different dates, they'd want to "lock" in the bittern and the behavior,
but not the point).
I could probably take this to another level of normalization, but I'm looking
to avoid that unless it would make things significantly "better"- the users
are used to being able to lock whichever fields they need to, thanks to the
previous app (as an unfortunate side effect, everything got dumped to one
table, making reporting & analysis rather a pain).
Any suggestions? Thanks in advance!
I'm trying to figure out whether it's possible to set up certain controls
(textboxes and comboboxes) to "lock in" certain inputs when the user checks a
box. (this sounds weird, I know, but we had a third-party app, no longer
supported, which did this).
So, for instance, we have the controls Date, Point, Species, and Behavior.
If someone went to Point 1 on 1/1/01, and saw five different species, each
doing different things, then we would want the user to be able to input the
point name and the date, indicate that they were to remain contstant til the
user changed them, then go and enter in species and behaivor information.
However, it's also likely that the user would have only one species at any
given point, or want to enter the data in reverse order (say, if they saw an
American Bittern at 8 different points, each with the same behavior, on one
or two different dates, they'd want to "lock" in the bittern and the behavior,
but not the point).
I could probably take this to another level of normalization, but I'm looking
to avoid that unless it would make things significantly "better"- the users
are used to being able to lock whichever fields they need to, thanks to the
previous app (as an unfortunate side effect, everything got dumped to one
table, making reporting & analysis rather a pain).
Any suggestions? Thanks in advance!