bb.donnay-software.com

It is not documented in the help file. But it appears to work similar to var2char() for arrays.

I use the dicryptosys library. Rather inexpensive. $100 our so. I use it for AES encryption. It is a win32 library.

Cliff

Sometimes oError:args is an array. I know I can do a dc_arrayview() or wtf to view the data. DC_Xtoc() only shows {...}. Is their a different function available to convert the array to a text string to show in a popup dc_msgbox().

Thanks, all for the help, especially Regan.

When I created a function and posted procname(2),procline(2) to cargo, prior to the break(oError), I got the line needed. Now I can make my dumb custom error handling better.

Cliff

Using ADS and without the error handler, I get the normal runtime error.

Do you have a small code sample to illustrate.

Maybe Roger can provide a code sample also.

Unfortunately procname(2), procline(2) point to the calling function 2 levels up.

bExtract:= {|a,b,o,x| S_Extract(Getlist,oV)} // Extract configured data

Which is the code block activated by the DCPUSHUBUTTON.

I did and tried using their code exactly. It appears that when you use a customer error object, it affects the stack. Must have to do something with the recover using, but the error object does not have a variable for the error line number. They check for a call stack method existing, but in the cus...

This is what I get. First line is the display of the error object. 2nd line is the line calling the function I am in, PRCOMMADEL(). The error line is not there.

That is what I am doing, but in the custom handler all I get it the line displaying the error object info as procline(0), then procline(1), is the calling function, but not the error line that caused the break(e) to be excecuted and then the RECOVER USING. How do I get the error line.