BUG: Filter-By-Form changes the value of unbound controls

[Allen Browne]

Filter-By-Form changes the value of unbound controls at will..

Steps to reproduce behaviour
------------------------------
1. To any form, add an unbound toggle button or a check box
that has a DefaultValue of True.
3. Switch to Form view. Confirm the button/check box is True.
4. Click the Filter-by-Form icon (toolbar).
5. Apply a filter or cancel as you please.
Access has changed the button/check box to Null.

How can I trust software that alters the value of controls as it
chooses?

[Gary Labowitz]

Interesting. The DefaultValue is the value to be assigned to the control on
a new record.
An unbound control doesn't save its value anywhere. So, anytime a record is
retrieved fresh, and by that I mean Queried or Requeried, there isn't any
place to get a value for it. Can't use DefaultValue, the record already
exists. Don't have data for the control from anywhere else (like the
database). What would you put in a control to indicate there isn't any valid
data for it?
I suggest Null is as good as any.
Just a thought.
--
Gary (MCT, MCPS, MCSD)
http://www.enter.net/~garyl/ for references to good books
Contribute to ga...@enter.net
ICQ 6375624
Allen Browne wrote in message <35DD15E6...@odyssey.apana.org.au>...

[Allen Browne]

Thanks for the reply, Gary.

This problem is not with the DefaultValue property. Access resets
unbound boolean controls to Null regardless of how you originally
set them true--whether you originally set them with code or by
clicking them with the mouse, etc.

Moreover, requerying the form does not reset them to Null.
The bug is in Filter-by-Form.

My beef is that some users rely on unbound controls as "variables".
I cannot imagine *any* programming language lasting very long if it
resets people variables when it feels like it! Along with the myriad
of other bugs that are still appearing in Access, I am beginning to
lose all confidence it the product.