>How about an OLE container that includes the hWnd and hDC of the host window?

>I know that VFP was targeted at being a cross platform dev tool (hence some of the unavailable or difficult to obtain windows standard stuff) but I think that some consideration should be given to some windows standard container (it is an outstanding DB dev tool that primarily suffers from the aforementioned incompatibilities).

>With the financial realities of the development world being what they are, control developers are only obliged to test the compatibility of their product with the dev tools where the majority of their market resides.

>If VFP hosted OCXs EXACTLY as VB does (no cursing until I'm done rambling) the current VFP development community would benefit from a wider selection of solutions and VFP would enhance its reputation as a serious development platform.

>OK...shoot me if I'm wrong, but I believe the majority of us program for the MS Windows platform and I believe that many of us spend time working around these limitations.

>What percentage of threads are directly or indirectly related to VFP's quirks with OCX, API, printer or driver issues?

>VFP is an excellent development tool that could only become better with a little 'MS Windows Mainstreaming'.


>Have A Good Day,


>ED

HI ED.
Tell us how you really feel. :)