Backwards code works Forwards? Why?

[MyWaterloo]

I quickly put this code together to test if it would disable some of my functions OnChange when my text box (purchase order number) is empty...and if it would enable those functions when I added data to my field. The funny thing is that if you read the code it actually runs in reverse! When my field is null it is suppose to disable...inste ad it enables...Why? So I put my code in to do the opposite of what I want and it works!?!?! I don't mind having my code in logical reverse as long as I get the results I'm looking for...but...I don't get it....???? ;-)


Forwards: (works in reverse and enables features when Null)

Private Sub PurchaseOrderNumber_Change()
If IsNull(Me.PurchaseOrderNumber) Then
Me.Check107.Enabled = False
Me.Check111.Enabled = False
Me.Text77.Enabled = False
Me.Label119.Visible = True
Else
Me.Check107.Enabled = True
Me.Check111.Enabled = True
Me.Text77.Enabled = True
Me.Label119.Visible = False
End If
 
End Sub

Backwards: (disables features when null)

Private Sub PurchaseOrderNumber_Change()
If IsNull(Me.PurchaseOrderNumber) Then
Me.Check107.Enabled = True
Me.Check111.Enabled = True
Me.Text77.Enabled = True
Me.Label119.Visible = False
Else
Me.Check107.Enabled = False
Me.Check111.Enabled = False
Me.Text77.Enabled = False
Me.Label119.Visible = True
End If
 
End Sub

[FishVal]

Hello.

I suggest you to perform a little experiment - add two controls on the form and in PurchaseOrderNu mber_Change event handler assign PurchaseOrderNu mber.Value property and PurchaseOrderNu mber.Text property values to them.

Regards,
Fish.

[MyWaterloo]

@FishVal
Ooook that was interesting.... .So....what is that showing me. A little bizarre, but I have no idea what these results tell me... =-)




"So, where did you learn Access?"

"Learn Access? Who? Me?"

[FishVal]

@MyWaterloo
I guess it explains why your code behaves in a way you don't expect.

Kind regards,
Fish.

[MyWaterloo]

@FishVal
I don't understand how it explains what my code is doing. Why do the two controls behave the way they do? Why does the code work, but in a way that appears to be in reverse? I just don't see how the two controls reveal why the code behaves the way it does.






"I can design a fantastic looking form for you. With buttons and menus and everything."
"What do they do?"
"What?"
"The buttons and menus."
"I have no idea, but they sure look good."

[MyWaterloo]

OK. I see that (for whatever reason I don't know) this current process of mine will not work. I guess I'm at a dead end. I was hoping to disable certain features if one of my fields was not filled in i.e. null. =(

[FishVal]

@MyWaterloo
I think it is quite straightforward .

PurchaseOrderNu mber.Value property is a default property you implicitly invoke when checking condition for enabling/disabling.
This little experiement shows you what this property returns when PurchaseOrderNu mber_Change event fires thus making clear why the code behaves the way it behaves. At the same time value returned by PurchaseOrderNu mber.Text property is , I guess, a more relevant criteria for making decision whether the controls should be enabled or disabled.

Does it make more sense now?

[MyWaterloo]

Yes, it kind of makes sense to me. I guess what it really means is that I need to come up with some other way to disable my print buttons if my P.O. number field is null. Any ideas? (Thanks for the lesson.)

[mshmyob]

subscribing just to watch the fun.

cheers,

[NeoPa]

Did the values ever get posted?

Fish & the OP seem to be discussing something they can both see but I for one, don't see any values posted (Emperor's clothes! I was never one to try to hide my ignorance so I will always ask the questions).