Chris
That's the way to go, but personally i use chr(13)+chr(10) for each line
Jaime
>Thanks
>
>Thats all I need - the simplest way for me is to just wrap the "xml" etc and "text" etc around a message of my choosing.
>
>Something like this - Do I need the CHR(13) on the second line in order to ensure the "text" tag starts correctly under the header, or will it get corrected as it arrives at the target (calling program)?
>
>
> CATCH TO lo_Exception
> lcErrorMsg='<?xml version = "1.0" encoding="Windows-1252" standalone="yes"?>' + ;
> CHR(13) + ;
> '<text>' + ;
> 'Error: '+TRANSFORM(lo_Exception.Errorno)+' - '+lo_Exception.Message+;
> CHR(13)+;
> 'Line #: '+TRANSFORM(lo_Exception.lineno)+' - '+lo_Exception.linecontents+;
> CHR(13)+;
> 'Function: '+TRIM(lo_Exception.procedure) + ;
> '</text>'
>
> * Used to return meaningful error message to calling program
> RETURN lcErrorMsg
>
Why do programs stop working correctly as soon as you leave the Fox?