Hi George,

>1.) VFP could dump the current way it handles windows messages, meaning less code to be maintained by MS and possibly resulting in a smaller run time DLL.

As much as I would like to see this, I would think that it requires almost a rewrite of the kernel of VFP. After all, internally VFP is still a cross-platform tool that probably contains much of the code of FPW 2.6. Changing this to make use of native Windows functions, especially the GDI, means that probably a lot of working code has to be touched. I'd expect at least as many problems as we had with the first release of VFP 3, maybe even more.

>This would also mean that certain problems with windows properly being refreshed would disappear.

I really like to see a correctly firing paint event! *s*

>3.) Would provide for better and more reliable interaction with ActiveX controls.

In which way?

Christof