>Ed,
>My problem is why is NT capturing these errors but Win95 is not - same code, same EXE. I've had to do several different workarounds just to make code work on NT.
>

There are internal differnces in the NT basae operating system and the Win9x family stuff; NT has built-in facilities to trap a number of specific types of errors at the operating system level that don't exist in the Win9x world - security objects, the meaning of some options that are completely unimportant in Registry manipulation (like the level of privilege a given access has to alter, or in some cases, even read, parts of the registry.) NT is much stricter in disallowing requests to access memory or hardware ports not belonging to the VFP process, too.

I've heard rumors that many of the problems causing the C5 error are VFP's memory management core; perhaps some changes are planned for the garbage collection mechanism, or for clearly indicating when memory associated with a released object can be reused. That's all wild speculation.

If it's true, hopefully the maintenance relase, when it ships, will correct many of the not easily reproducible C5 errors.

>>Keep dreaming, Barbara; it's an error captured by the operating system that flat out kills VFP, like a GPF...