Freechain Issue

[Nancy Palmquist]

Doug,

I was just looking at the responses.  I had a suggestion on the logging 
option.

I had cause to try to hunt down a memory crash bug and what I did was 
make a file that had the user name, date, time, what they were doing, 
and any other info that you thing might be helpful.  (no indexes please 
in this file.)

When the user starts the routine that is questionable, I write a record 
in this file.  I remember the record number in a variable.
When I finish the routine I delete the record I wrote.  Always put this 
step after the write commands that affect the file in question.

Anyone that leaves without reaching the proper end, will leave a record 
in this file.  It may help you see if a user, or process is aborting or 
crashing without finishing.  Might point out a logic flaw or just bad 
training but it might help you.

You might find the information you collect helpful.  It sure helped us.

Nancy

-- 
Nancy Palmquist 		MOS & filePro Training Available
Virtual Software Systems	Web Based Training and Consulting	
PHONE: (412) 835-9417		   Web site:  http://www.vss3.com