events do not fire (1 Viewer)

[dreamdelerium]

hi everyone. im looking for some help. when i programatically set a value for a control (ie, check a check box) why doesnt the associated event fire?

for example, if i programatically set checkboxA to checked, the checkbox will become checked but the onclick event doesnt fire. how do i get it to do this.

im creating a set of forms in access 2003

 

[DCrake]

Is your checkbox part of an option group?

view the properites of the checkbox and scroll down to the On Click event if is states [Event Procedure] clicck on the build button and examine the code. Place a breakpoint on the first line then save the form and retry.

If there is no event on the On Click property then the procedure is located elsewhere.
David

 

[dreamdelerium]

i think i should explaine more:

as an ex, i have a form with a check box and a text box. the check box has thsi onclick event:

Private Sub CheckBox1_Click()
If Me.CheckBox1.Value = -1 Then
Me.TextBox2.Enabled = True
Else
Me.TextBox2.Enabled = False
End If
End Sub

if the user checks the check box, this work
but if i have a button with this event:

Me.Checkbox1.value= -1

i would expect the checkboxs onclick event to fire (when the button is pushed), making the textbox.enable to be set to true, which doesnt work

 

[DCrake]

The code you need is either:

If Me.CheckBox = True Then
Me.TextBox.Enabled = False
Else
Me.TextBox.Enabled = True
End If

Or:

Me.TextBox.Enabled = Me.CheckBox

Or:

Me.TextBox.Enabled = Not Me.CheckBox

David

 

[gemma-the-husky]

if you set text box oe other control values in code - no events fire (although the record will become dirty, or new)

the events only fire when you interact with them directly

 

[dreamdelerium]

thats what i was afraid of. so, no way arround this huh?

 

[MSAccessRookie]

thats what i was afraid of. so, no way arround this huh?

What about creating a common procedure/function to execute? If you set the value in the code, can't you call the same procedure/function that would be called if the event had been triggered through normal means?

Note that if the code is small enough, you can always duplicate it, but that creates the potential for one version being updated and another not being updated if the procedure/function needs to be changed at some future date.

 

[missinglinq]

Whenever you do something like this, all you have to do is to call the event that would normally be triggered:

Private Sub YourButton_Click()
  Me.CheckBox1.Value = -1
  [B]Call CheckBox1_Click[/B]
End Sub