>Ed,
>
>Thanks for the info. I didn't know the C000005 error was actually a sort of GPF. I did see a lot of messages regarding this C000005 error and because of this i didn't want to release my software in VFP 5 but stick with 5.0a. And because i don't use much of the extended VFP 6 features there is not much reason to take the risk with VFP 6.
>
>One Question, though. Do you think VFP 5.0 is more stable than VFP 6 ? I really want to choose the most stable product before a realese my applictions.
>

For the moment, yes. Unless there's an overwhelming need for new features in VFP 6, I'm keeping my existing applications on VFP 5.0a, and waiting on VFP 6.1, hoping that it offers a more stable platform, and some key changes in VFP's behavior for implementing Automation.

There's a lot to like in 6, but I'm reluctant to release a new version of a solidly working application written, tested extensively and shipped in VFP 5 just because 6 is out and has already gotten more good press than VFP 5 did in its entire life. I'm using 6 for new projects, but for me, I've got a development platform that I understand well, a framework that I'm comfortable with, tools that cooperate with it, and a whole lot of code that's been pounded on with VFP 5.0a. I'm really waiting on at least a real service pack or .1 release to ship before making the shift.