error trapping

[dcurrier]

I loaded up the simple VB6 example and started looking the control over.

Is there a way to indicate an invalid symbol? I didn't see any OnError type events for bad symbol, dropped connection, or other server or data errors.

The only thing I noticed in the Object Browser was
"IsValidSymbol" which is listed as a method rather than a property like IsHistoryReady. It also expects the Symbol as a parameter rather than lHandle.

I experimented with it a bit and it always returned a zero.

How can I handle these type of errors?

Thanks,

David

[Guest]

IsValidSymbol() is the only way to determine if it is a bad symbol.

[dcurrier]

IsValidSymbol

Thanks for getting back so quickly. You live in this room?

I went back and saw it was a function. It apparently returns a Boolean. I got it to work.

I didn't see it listed in your documentation.

Are there any other errors that get trapped?

Thanks,

David

[Guest]

It's my responsibility (among others) to monitor this forum. George, however, probably answers questions better than I do.

This function doesn't really trap an error. It's just sending the "No Data" message that you see in eSignal back as a boolean.