Thanks. I've actually changed the focus of what I'm looking for, but this thread isn't going to waste because I'm learning commands that I'm sure I'll use in the future.

Thanks,

Michelle

>Not sure if this will help, but in our error handler, we use the following native VFP functions to capture system state:
>
>PROGRAM() - obvious
>LINENO() - line number of program with offending statement/command
>MESSAGE() - error message
>MEMORY() - spits out all open files, indexes, memory variables, their values, etc..
>
>HTH,
>Phil