>I "ran" it, and while it "burnt" a processor for a while and killed VFP 7.0 SP 1 eventually, it didn't cause any system errors. (Note: I'm running XP Pro on a dual processor system.) I also noted that when I went back into 7.0, my _command.prg file had been "reset" - it was totally cleared / erased.

I got the same problem under Win2kPro on single CPU (Pentium III @ 700 MHz), but also after some playing with it - my VFP7 SP1 stoped starting - I always got Fatal Exception when try to run it. I have made tests from the command window directly.

Note that I came upon this problem in a real-world application (the code was not the same - but similar - evaluate that should return very long binary string) working under Windows 98 SE system (in some cases it just hangs or quits immediately).

I think this is combined limitations of evaluate function and character string length. The problem is that VFP does not raise an error (that I can trap programaticaly) but just quits immediately or raises fatal exception. Hopefully we have noted this error before posting the update to our customers.

Regards