See if starting VFP8.EXE with the -a switch helps at all.

Also, it would help if we could some crash info from you.

1. Go to Control Panel/Administrative Tools, and open Event Viewer. Look in your Application event log. You will see 2 events from the time of the crash with IDs 1000 and 1001, with the 1001 being newer. Please open the 1001 event, and you will see text like this:

The description for Event ID ( 1001 ) in Source ( Microsoft Visual FoxPro ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: 12697551.

2. Please send through the number at the end of that text in your event log item, which may sometimes be referred to as the 'bucket ID'.

3. If you chose not to send in the report when you got the crash, you will still have an EventID 1000 from when the crash occurred. It will contain text like this:

vfp8.exe, 8.0.0.2521, vfp8.exe, 8.0.0.2521, 0041863f


Send through this text if you don't have a bucket ID. Either of these can help us pin down the cause of the crash.

>Jim
> It is NOT foxuser related. Two more details that may be important:
>
>Crashes often when tracing through type 2 formsets (fp26-converted screens)
>Crashes much more often on some machines than others, all of them same hardware and OS.
>
>I suppose that MS did not spend a lot of time testing these very old type of forms...
>
>Regards!