New records have null check box

M

Martin

Here's a funny thing (if you're interested!): 97 format databases that have
either been opened in or converted to 2000 format show check boxes as null
(greyed-out) for new records rather than the usual False (or empty) which is
what shows for new records in a 97 database opened in 97 or a 2000 database
opened in 2003.

This has caused me problems because I have Form_Current code that responds
to whether a check box is true or false to en/disable a combo box. Easily
fixed of course - I'll just include an If(IsNull(checkbox1)... - but enough
to cause the form to stop working.
 
M

Martin

Scrap that fix - it's safer to change the default value of the check box in
the form to False in case there are any other knock-on effects.
 
D

Duncan Bachen

Martin said:
Here's a funny thing (if you're interested!): 97 format databases that have
either been opened in or converted to 2000 format show check boxes as null
(greyed-out) for new records rather than the usual False (or empty) which is
what shows for new records in a 97 database opened in 97 or a 2000 database
opened in 2003.

This has caused me problems because I have Form_Current code that responds
to whether a check box is true or false to en/disable a combo box. Easily
fixed of course - I'll just include an If(IsNull(checkbox1)... - but enough
to cause the form to stop working.
Click to expand...

Rather than check the value of the checkbox, why not look at the
underlying data?

Null is *not* the same as False. So having the checkbox greyed out
indicates that no value has been store (either true or false). With a 3
state checkbox, this is doing exactly what it's supposed to do.

If you expect there to always be a value of False if True isn't
selected, then setting it's default value to False is one way of
handling that.
 
Top