Jim,
Madre de dios, are you suggesting that it won't catch a misspelled variable, i.e. an undefined variable, anymore?
I'll bear it in mind.
BR
Peter
>>In the explanation for the error it says:
>>
>>Free some memory currently in use and try this operation again.
>>
>>Yes,I'd love to, but which memory? Where? How? :)
>>
>>All I can see is, that the app- (VFP 8 SP1) - gobbles up memory when I activate / deactivate certain windows, but I cant' seem to pin it down to anything specific.
>>
>>Any and all suggestions are appreciated.
>>
>>TIA
>
>****
>I've had this error come up recently when I converted my apps to Version 8. Basically in every case I found that my coding was wrong - that I had made a mistake that wasn't caught in the editor - a misspelling of a variable or something .... so when i ran the exe version, it got this error. When I debugged it with the development version I found out the line it was hung up on.
>
>So... look to your code for an error that it can't quite figure out...
>
>Jim.
Peter Pirker
Whosoever shall not fall by the sword or by famine, shall fall by pestilence, so why bother shaving?
(Woody Allen)