forms

[Alice]

Hi there, I'd appreciate some advice on a problem i'm having......
I've got a custom form, and a button added as an event procedure to add a new record to the database. One of the items on the form is a tick box, which is not cleared when I press for a new record. How do I get it to clear the tick box when I request a new record? It's driving me mad!
Many thanks, Alice

 

[Corticus]

Hi!

Right-click on the 'new record' button and select 'build event'. You should see something like:<pre>DoCmd.GoToRecord , , acNext</pre>
after this line add<pre>Checkbox1 = False</pre>
substituting Checkbox1 with the name of your checkbox.

That should do it!

edit:
oh yeah, I meant to suggest changing the default value of the Checkbox to 'False', my bad!

HTH,
_________________<EMBED width="118" height="52" src="http://corticus.biz.ly/CorticusLink.swf"></EMBED>
This message was edited by corticus on 2002-12-09 14:32

 

[BrentA]

Hi. It's not normal behavior for Access to default to checking a checkbox. There are two simple reasons for this to happen: there's a "default value" set in the table (which is probably why this is happening) or a default value set in the control properties.

The previous reply will work (although you might want to change the line to "Me![Checkbox1] = False" in case the name of your control is "Check Box 1"), but it might be easier to just set the Default Value property of the control to 0 (which is the numeric equivalent of "False" to Access -- and True = -1). That way you don't have to mess with the code.

HTH,

Brent

 

[Alice]

Thanks for those guys, but neither of them seem to work - the defaults are set to false, and i've tried the code you suggested, and it won't work for me - my understanding is v v limited. Is there any way i can send the form to you?
v v frustrated alice-
+

 

[Tanis]

Just a thought. Try taking out the defaults for the check box in both the table and the form property

 

[Alice]

Thanks for that guys, seems to be working now.....not really sure what I've done, but it's fixed! Many thanks, Alice