Strange behaviour with if statement

[tborn]

Hi there,
Not sure if any one has experienced this before and can tell me what's
wrong with this statement:
if verified = false then dataObjects.Has Error = true
This is all on one line and verified is defined as a boolean variable.
Irrespective if verified is set to true or false in ALWAYS executes
dataObjects.Has Error = true.
Following code works as expected and dataObjects.Has Error = true
executes only if verified is set to false.
if verified = false then
dataObjects.Has Error = true
end if
To top it all of, I use the construct

if [expression] then [do something]
at other places in the program and it works fine.
Any ideas?
Thomas Born

[Greg Burns]

Cor,

I was going to write back and say that the Finally block had nothing to do
with it. (Just happened to be in my example). But when I tried it without
the Finally, it doesn't do it! It is CRAZY! :^)

Greg

"Cor Ligthert" <no**********@p lanet.nl> wrote in message
news:uf******** *****@tk2msftng p13.phx.gbl...

Greg,

It was exactly as you said yesterday what you said and thought that I got
not that behaviour, tomorrow I get it, with this as well,
\\\
Try
Catch ex As Exception
Finally
If 0 = 1 Then MessageBox.Show ("hello")
End Try
///
And only in the Finnally block, and it will not be exectuted, it shows it
is
executed.

In your example it can be the right situation when this error on the open.
However in this case, when I set it in a three line If statement, it
behaves
in another way as you said, crazy.

Cor

I just tried you exact code and it behaves the same whether I disable the
first close or not.

Understand, nobody is disputing that if the connection is already closed

it

will NOT try and close it again. The code works properly.

It is simpy this; if you step through with the debugger it ALWAYS

highlights

that cn.Close on the other side of the Then. It appears that it is
exectuing it, whether it is or not.

Make sense? I added a screen shot (and simplified the If expression)

Greg

"Cor Ligthert" <no**********@p lanet.nl> wrote in message
news:OW******** ******@TK2MSFTN GP12.phx.gbl...

> Greg,
>
> I changed it to this,
>
> \\\
> Dim cn As New OleDb.OleDbConn ection("Provide r=Microsoft.Jet .OLEDB.4.0;Data > Source=C:\whate ver.mdb")
> cn.Open()
> cn.Close()
> Try
> Catch ex As Exception
> Finally
> If Not cn Is Nothing AndAlso cn.State = ConnectionState .Open
> Then cn.Close()
> End Try
> ///
> I have a different behaviour when I disable that first close.
>
> Cor
>
>> No, you got to do my example. The problem is when If Then is one
>> line,
>> no
>> End If.
>>
>> You won't be able to throw in a messagebox like you are trying. You will >> have to step through with the debugger.
>>
>> If Not cn Is Nothing AndAlso cn.State = ConnectionState .Open Then
> cn.Close()
>> <-- all one line
>>
>>
>> Greg
>>
>>
>> "Cor Ligthert" <no**********@p lanet.nl> wrote in message
>> news:Ol******** ******@TK2MSFTN GP12.phx.gbl...
>> > Greg
>> > I tried this and no strange results
>> >
>> > \\\
>> > Dim cn As New
> OleDb.OleDbConn ection("Provide r=Microsoft.Jet .OLEDB.4.0;Data
>> > Source=C:\whate ver.mdb")
>> > cn.Open()
>> > cn.Close()
>> > Try
>> > Catch ex As Exception
>> > Finally
>> > If Not cn Is Nothing AndAlso cn.State = ConnectionState .Open >> > Then
>> > MessageBox.Show ("Is showed when cn.close is
>> > disabled")
>> > End If
>> > End Try
>> > ///
>> >
>> >
>>
>>
>
>