>
>Really? I hardly ever have problems with VFP 5, which is what we do most of our development in. I switched to VFP 6 SP3 for an in house program I wrote and it crashes all the time. Mostly the C...5 error, sometimes just freezes, and a new one is it sometimes says something like "invalid seek offset" when I close the program and I have to kill the program with the task list. I wish I had stuck to VFP 5.
>
>Michelle
Michelle,
VFP 6 fixed LOTS of bugs that had been in the product since the 2.x days. With VFP 5, you'll get GPFs instead of C5 errors. VFP 6.0 is intercepting GPFs and showing them as C5 errors. 6.0 also has MUCH better support for ActiveX and COM. The multi-threaded COM DLLs are a must.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer