>>About this... it always comes with a long list of system variables, specially those for DOS printing system, which we don't care about. So I cut them out:
>>
>>

		LIST MEMORY TO FILE (THIS.cJunkFile) NOCONSOLE
>>
>>		IF FILE(THIS.cJunkFile)
>>			LOCAL lcLeftDelim, lcRightDelim, C
>>			lcLeftDelim="Memvars"+0h0d
>>			lcRightDelim="variables available"
>>			C=STREXTRACT(lcLeftDelim+FILETOSTR(THIS.cJunkFile), lcLeftDelim, lcRightDelim,1,1+4)
>>			REPLACE mMemory WITH C IN ErrorLog
>>			ERASE (THIS.cJunkFile)
>>		ENDIF
>>

>>
>>>I am taking notes of all suggestions. And will check out this PSR.EXE. However, I can't make my application automatically email; many clients "warn" that they do not like this. Probably mainly concerned about losing confidential information. I periodically connect and check myself.
>>
>>Alternately, you can arrange for error logs (one per error, or one per user session) to be made in a predetermined folder to which you have FTP access (and can check for it periodically and automatically) or to have these files FTP'd to your predetermined URL. Disclose this to admins and tell them to deny access to this location to yourself only (in the first case), or limit the FTP to your URL only (2nd). Let them log it any way they like it.
>
>LIST MEMORY LIKE * is a lot easier and accomplishes the same goal of omitting system variables.

Nice trick! I'll incorporate that.