Unhandled exception encountered in callback automation code

[Ehaviv]

Hi

When I run a callback dll this hapen.
can someone explain why

This statement throw this exception
unhandled exception encountered in callback automation code

If atts(attrNdx).Title <> myAttrib Or attrqty <> 1 _
Or part.GetStringUserAttribute(myAttrib, attrNdx) <> "1" Then
savedTimes(ndx) = 0
End If


and this not throw that exception

If atts(attrNdx).Title <> myAttrib OrElse attrqty <> 1 _
OrElse part.GetStringUserAttribute(myAttrib, attrNdx) <> "1" Then
savedTimes(ndx) = 0
End If

Or vs OrElse

I am very thank you.

 

[CADPat]

Hi @Ehaviv!

I can't answer why you see the exception, but the question of "or vs. orElse" is a general programming Q that can be found on-line.

In short, orElse is a "short circuit" version of the "or" checck, meaning that as soon as it finds an expression that is True, it jumps out and does not worry about the rest of the checks (regular "or" will run all checks before deciding what to do, even though it's enough to find 1).

Typically this is used when one check is more common or faster, and you'd put it first, saving time on the 2nd and later checks.

What does this tell me for you case?

That the first check (atts(attrNdx).Title <> myAttrib) is working fine, but there is a problem with the 2nd or 3rd expression that is causing the error.

 

[Ehaviv]

Hi CADPat and thank you

In the first time I used or as I use
in general.

and I got errors and I was upset
because I know the attribute title
and it's string value and the
Number of the same title is ok because
I filled it myself before journal
running.

I was upset until thinking to try orelse

Now the journal run ok with orelse.
for each of the tree conditions

But I am still upset why or throw error.

Thank you very much.

 

[CADPat]

Happy to hear it's working for you.

I don't do much programming, nor do I know what the rest of our code does, but from looking at the 2nd check you are doing, as you are checking for a string attribute, which happens to be "1", just wondering if the attribute might be getting processed as an integer instead of a string as expected. A pure guess, however, based simply on having heard people make such mistakes before.

 

[Ehaviv]

Hi CADPat

I will check that I don't fallen in that.

(I think it's a string. But not sure I need to check)

Thank you very much for your efforts to help.

Thank you.

 

[Ehaviv]

Hi CADPat

That's the problem.

The attribute is a string type and
I used an integer variable (by a mistake)
to collect it.

You helped me to get out of my upset.

Thank you very much.