Parentheses to evaluate True/False?

[cbrf23]

I'm trying to create a dynamic user form through vba. Since I'm not real familiar with forms, I downloaded an example to kind of reverse engineer. When going through the code, I noticed a line using a syntax I'm not familiar with:

CmdBttnDE.Enabled = (SpinButton1.Value > 0)

This code disables the button if the spinbutton1 value is not greater than 0. I didn't know you could do that...pretty cool trick. Seems more efficient then:

if not SpinButton1.Value > 0 then CmdBttnDE.Enabled = False

So, I'm wondering how exactly this syntax works. Does throwing parenthes around a statment like that automatically ask vba to evaluate the statment to true or false? I tested and the same line works with the parentheses removed... Anyone have any insight on this?

 

[Dan Waterloo]

The parentheses are there in order to make the order of evaluation clearer. You could also write

CmdBttnDE.Enabled = SpinButton1.Value = 0

Here, the rightmost equal sign is being used as comparison operator while the leftmost equal sign is being used as an assignment operator. The comparison has to be done first and then the result of the comparison gets assigned to the variable. But writing it as

CmdBttnDE.Enabled = (SpinButton1.Value = 0)

makes it clearer. And it would be necessary in a case such as

 X = Y = Z = W < V

in this satement X would end up being assigned either True or False depending on how the chain of evaluations of the variables to the right worked out. But I for one am not sure what the order would be - I would have to look it up because the order always seems to depend on whatever language you are working in. It's certainly clearer (for both the author and any subsequent reader) if the author imposes the order of operations using parentheses.

 

[cbrf23]

I see...that makes sense.

Thank you Dan!