>David:
>
>Thanks for the suggestion, that is exactly what I am trying to do. I am logging what I am doing and when the error occurs, and when I have more info I am going to open a bug report. Right now, I don't have enough details since it has happened at all different times

I've been using a tool that helps track this type of stuff down for a while now, and it does a phenomenal job of tracking everything - keystrokes, mouse movements, form context changes, etc. Perfect for find the sequence of events leading up to crashes, or recording user actions in detail during a long and complex series of event leading up to a bug. It's called WinWhatWhere Investigator, from WinWhatWhere Corporation. It does a great job of instrumenting any application to track user actions. The following is pulled from the intro to W3I's Help file:

Investigator’s unique ability to invisibly monitor all keyboard activity placing it in the context of the active window and application make it ideally suited for the investigative needs of law enforcement, government, business, and private individuals.
The data is presented in easy to read reports that include a raw keyboard output along with a "final copy" display that processes and removes all editing to replicate the final output of a document. The data is exportable making it accessible to a broad range of other applications for analysis and reporting.

Investigator employs stealth technology making it virtually undetectable and tamper proof. Deployed on a network, Investigator reports all activity on every workstation to a single database.
In addition to all keystrokes, W³ Investigator logs the user and computer name, each active program, window title, menus, buttons, check boxes, lists, etc.

Data Collected By Investigator


Workstation Computer name
User Login name
Date Date of entry
Start Start Time
Elapsed Time window was active
Keystrokes Number of keystrokes recorded
Caption Caption of the current control. This can be the window title, button caption, etc.
EXE Full name of program
Formatted Text Captured keystrokes with editing removed.
Raw Text Captured keystrokes with all function keys, arrow keys, etc.

Formatted and Raw Text

Raw Text is a display of the captured keystrokes exactly as recorded. Function, directional, control, and other special keys are translated into key descriptions. The formatted text has stripped all special keys and has processed backspaces, shifts, delete keys, etc.

You can contact them, and download trial copies of this and their other products at WinWhatWhere Corp's Web Page. It's probably one of the best tools of this kind I've ever run into, and at $100, one of the least expensive.

>
>Rob
>>Rob,
>>
>>If you have a set of steps that can cause the error to occur, you should send them to the bug report page, that's the only way Microsoft is going to be able to clean up the problem.
>>
>>>AMEN! I must get 4 or 5 of these errors every day, and when they happen is ridiculous! Today, I went to edit a form, and when I placed a control on it - WHAM! I re-start VFP (I am using 5.0a on NT), open the same form, place the same control, and everything is fine!
>>>
>>>I have seen lots of advice on this site about missing DCOM, ON SHUTDOWN, and FOXUSER.DBF issues causing this problem, but none of these seem to work or apply to me. I guess its too much to ask MS to actually do something about this