Hello -

Yes, VFP7 SP1 is used for development and clients either use VFP7 with SP1 or VFP7 runtimes with SP1. Client computing environments are NT or later, most are Win2000.

We still use one Win98 system for development. The problems can be recreated on any system.

The VFP6 versions still run (same EXACT code) with no errors.
We're past the putting out fires stage and are proactively changing coding practices.

The good luck wish is much appreciated.


>You don't mention it, so I'll ask. . .
>
>Do you have SP1 for VFP7 installed? If not, you should downlaod it, because it fixes some C00000005's.
>
>good luck
>
>
>>We are seeing C0000005 errors in VFP7 on a too frequent basis.
>>
>>The errors, including C000005, are appearing in applications now running in VFP7 that ran like a champ in VFP6 (VFP6 projects recompiled in VFP7). They are also occuring in applications built from ground up in VFP7.
>>
>>The operating systems are Win98, NT, 2000.
>>
>>Most problems, so far, seem related to using a variable without first initializing it. In some cases the variable was declared local and in others it was not declared at all. FoxPro always supported these bad habits in the past.
>>
>>Is anyone else noticing this?