T
Transient
I am utilizing MS Access 2000 on Windows XP Home.
I have a form that, among other controls, has a list box that has as its
RowSource a nested, named query. The query itself contains reference to a
text box control (called BidID) on the same form (so I can filter the info in
the list box based on the value of BidID).
Generally, the form behaves appropriately but, over time, as I work with the
form, the behaviour of the form becomes odd. When I switch from Design mode
to Form mode, it will begin to prompt me for the value of BidID (as if the
value is undefined and Access is treating it as an undefined parameter in the
underlying query). It's almost as if Access is trying to execute the query
that underlies the list box before loading the data into the form and then
populating the list box. Also, on occasion, when switching back to Design
mode from Form mode, I get the same prompt for BidID (there is no code or
macro or expression set for the OnClose and related events).
Eventually, Access shuts down entirely.
Even stranger, if I open the same DB in Access 2002 (in Access 2000 file
format) on a XP Pro machine, the errors/corruption does not occur. I've sat
the two machines next to each other and performed the exact same actions on
each and the Access 2000 version performs the odd behaviour while the 2002
version does not.
I've opened a brand new DB and imported the objects but still have similar
behaviour.
So, first, I'm assuming I have something related to the form that is
corrupt. How do I determine if it is the whole form, the list box (or other)
control, or the query that underlies the list box? Or do I need to just
recreate everything related to the form from scratch?
Also, why is the behaviour different b/w 2000 and 2002? Should I just
continue forward using 2002 or is it in some way masking the corruption in a
way that is going to burn me later?
Thanks for any input.
I have a form that, among other controls, has a list box that has as its
RowSource a nested, named query. The query itself contains reference to a
text box control (called BidID) on the same form (so I can filter the info in
the list box based on the value of BidID).
Generally, the form behaves appropriately but, over time, as I work with the
form, the behaviour of the form becomes odd. When I switch from Design mode
to Form mode, it will begin to prompt me for the value of BidID (as if the
value is undefined and Access is treating it as an undefined parameter in the
underlying query). It's almost as if Access is trying to execute the query
that underlies the list box before loading the data into the form and then
populating the list box. Also, on occasion, when switching back to Design
mode from Form mode, I get the same prompt for BidID (there is no code or
macro or expression set for the OnClose and related events).
Eventually, Access shuts down entirely.
Even stranger, if I open the same DB in Access 2002 (in Access 2000 file
format) on a XP Pro machine, the errors/corruption does not occur. I've sat
the two machines next to each other and performed the exact same actions on
each and the Access 2000 version performs the odd behaviour while the 2002
version does not.
I've opened a brand new DB and imported the objects but still have similar
behaviour.
So, first, I'm assuming I have something related to the form that is
corrupt. How do I determine if it is the whole form, the list box (or other)
control, or the query that underlies the list box? Or do I need to just
recreate everything related to the form from scratch?
Also, why is the behaviour different b/w 2000 and 2002? Should I just
continue forward using 2002 or is it in some way masking the corruption in a
way that is going to burn me later?
Thanks for any input.