>After reading this thread, I would like to see VFP 7.0 to be on par with the >rest of VS product. Comprehensive support for all ActiveX variation (like >containership ActiveX).
The problem is the ActiveX vendors not following standards.
>Real Windows Control (buttons, toolbars, checkbox ,etc) and GUI interface. >This is important if you want to use automated QA programs.
Are you sure you want this? It will slow down your application and the native Windows controls don't have as many events, methods, and properties available.
>User replaceable FOX errormessages.
Look at Error event and ON ERROR. For a complete explanation of error handling in VFP, look at the whitepaper at
www.stonefield.com.
>Ability to build VFP application into ActiveX component not just COM/DCOM >component. It is a shame that a good development tool and language is left >behind with such glaring deficiencies. Thanks.
Requested many times. The response from the VFP team has always been "Why do you want to do that?"
>
>Regards,
>Kueh.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer