Changing Values without Firing Events

Hello, I have a headache. I have so many controls on this form and they all interact with each other, but there is one problem. I can't change the contents without triggering an event. For instance, I am displaying data from a DB and I put this:

Code:

---

chkTaking(0).Value = True

---

But because chkTaking(0) has a click event that is built into it, it runs when I say that which produces errors. Is there a way that I can change the .Value of the control without triggering its event?
Thanks a lot.

I would create a form-level boolean variable that you could use to know when to bypass such events.

or maybe something like this:

chkTaking(0).Tag = "No"
chkTaking(0).Value = True

then in the Check or click event whatver:

If chkTaking(Index).Tag = "No" Then chkTaking(Index).Tag = "": Exit Sub

But then how would the user be able to see that it was changed?

IF you changed it by code (Tag = "No"), then it would not register as a click, but it would still appear checked. IF you didn't (Tag = "") then it would do whatever was in the event.

Quote:

---

Originally posted by Lethal
I would create a form-level boolean variable that you could use to know when to bypass such events.

---

This is how I handle things too... it's probably the easiest to implement, and it works great. ;)

Me two.... I cannot think of a better way. It's pretty effective.

I have to admit, the Tag-way also works... but only if you're not using it for something else.

VB Code:

' In Declarartion Area
 
Dim BOOLCANCEL as Boolean
 
' In Click Event of control you want to handle
 
If BOOLCANCEL = FALSE Then
 
' Perform the click event...
 
' When setting something you know will fire click event use : 
 
BOOLCANCEL = TRUE
 
' Run your code
 
BOOLCANCEL = FALSE

Does this make sense?

I understand what you are saying. That would probably work. I just thought that there might be a better way. How would the tag way work, just for knowledge.
Thanks a lot.

i showed you how the tag way works, up several posts.

Quote:

---

Originally posted by evlich
I understand what you are saying. That would probably work. I just thought that there might be a better way. How would the tag way work, just for knowledge.
Thanks a lot.

---

You could use the Tag property, but if you want to use TAag for another use, you'd be limited. It is still best to go with the form level variable..

Quote:

---

Originally posted by James Stanich

VB Code:

' In Declarartion Area
 
Dim BOOLCANCEL as Boolean
 
' In Click Event of control you want to handle
 
If BOOLCANCEL = FALSE Then
 
' Perform the click event...
 
' When setting something you know will fire click event use : 
 
BOOLCANCEL = TRUE
 
' Run your code
 
BOOLCANCEL = FALSE

Does this make sense?

---

I agree with James I think this is the easiest and cleanest. I call my boolean varialble "ClickedByUser"

VB Code:

Dim ClickedByUser as boolean
 
Sub Something()
 
'Call the command1 click event
ClickedByUser = False
Command1_Click
 
End Sub
 
Sub Command1_Click()
 
'see if user cliced me or program clicked me
If ClickedByUser Then
   'user code here
Else
   'program code here
   
   'reset my variable
    ClickedByUser = True
End if
 
End Sub

See yet another user who agrees with the form level variable...;)

blnFreezeEvents for me. Wth Tag you would have to set the tag for every control that would be affected directly or indirectly and then reset the tags (not in the events but) only after it is OK to have the events called again. A public flag works best for me.

Thanks a lot. I got the form level variable to work. Appreciate all your help.

For waht itws worth, you are welcome...

My suggestion, and what i have been doing to get around your problem is to include a "Friend" proerty so that you can change the value without firing the event.

so the user uses this
chkTaking(0).Value = True

Public Property Let Value(newValue as Boolean)
m_Value = newValue
Raiseevent ValueChanged()
End Property

you use
chkTaking(0).SetValue = True
where SetValue is something like
Friend Property Let Value(newValue as Boolean)
m_Value = newValue
End Property

Gary007...

Isn't that a long work-around to what we have already posted?

My method quite possibly is a long work around but it saves on a variable, and one less thing that could go wrong, especially when you start doing multi threading and things like that. When you have variables that control the behaviour of an object things can get very tricky when you get into multi-threading. If you have two threads trying to change the property using your method, one raising the event and one not, you will find that things dont act the way they should. The event may fire once, twice or not at all depending on which thread got their first and which one left first.

But on the other hand if you are not multi-threading the other method is fine, but you must remember to set the variable, then clear it again after you have made the change to the property. Two things to remember to do, one if you just remeber to call the "friend" method instead of the "public".

They each have their draw-backs, i do admit that.