David,

Thank you so much for your response.

>1) You didn't mention the version of VFP you're running. Is it VFP 6 with SP3 applied?

Yes, VFP6 SP3

>
>2) How is the app being installed, specifically?

The errors are being replicated under the development environment so, if I understand your question correctly that is not relevant. The application itself is a runtime version installed using VFP's setup wizard generated stuff. Real standard.

>3) You said->>The major process that always completes before the symptoms occur is a SCAN with a large number of processes w/in the loop. These processes include several different SQL SELECTs, and BEGIN/END TRANSACTIONs (not nested transactions though). When the number of iterations of the scan is low, the environment stays healthy and subsequent processes finish. When the number of iterations is 1400 (possibly less but certainly at 1400) then subsequent processes fail as outlined above.
>
>Are the subsequent processes that fail also going through 1400 or more iterations before erroring out, or does the failure happen early in the process? IOW, even if the above SCAN is suspect, maybe it's not the real cause. Are the failure processes in a loop or SCAN?
>

After the "big scan" stuff, it fails before any other reiterative process starts. There is another one that follows but it doesn't get that far. It goes into a method where I get the errors with the variable declaration. If I skip that method by commenting it out then it hits other non-reiterative code and that is where I get the "property not found" errors.

My conclusion is that the "big scan" is totally hosing the environment, but how or how to avoid or how to fix is the "big question". there is absolutely now way to code around the bad environment. It has to be either fixed or prevented.

Thanks again and any other ideas are greatly appreciated!!!