>>Is there any way of accessing the contents of memory variables other than LIST and/or DISPLAY?
>>
>>I cannot use these commands (without crashing the client) in a VFP COM DLL.
>>
>>TIA
>
>Try DISPLAY MEMORY TO < filename > NOCONSOLE. Don't forget you can use LIKE to specify a skelton to match.
>
>No screen I/O should be generated. Admittedly, I haven't tried this from within a COM object, however, I've been able to generate text files within them. I'm guessing that this shouldn't be any different.

Guess I have to do some more testing. Initially LIST MEMORY TO FILE crashed the client several times (that's the last thing I added to the error handler) and Dr. Watson reported something about ".. not allowed in .. mode" which lead me to believe that it was an error about having a UI command on the DLL.
But now that I tested with DISPLAY MEMORY it works intermittently.

I'll go with AERROR() info for now and in the mean time I'll keep testing LIST & DISPLAY. Although the memory variables help a lot for debugging.

Thanks.