Craig,

That has always been my beef with VB. After a developer invests many man-years in mastering and developing with a VB version, MS makes his code incompatible with the newer version. It has happened before more than once. It happended big time from VB6 to VB.NET. The VFP team on the other hand, as you know, always made a point of keeping new versions backwardly compatible.

I hope that this time, when a developer moves to newer versions of VB that his WinForms code does not become incapable of running. But don't count on it. It is all about preserving MS's revenue stream, I have always thought. They haven't cared particularly about the developer's code that they made incompatible. Make the hampsters keep running while staying in the same place, and all in the name of progress.

Sorry, but that is how I see it.

Alex



>The future of WinForms in doubt with WPF coming along.
>
>>Thanks Craig,
>>
>>Guineu is still in its infancy, but I will keep an eye on it.
>>
>>Take a look at Visual WebGUI's site, or Rick's blog about it. It is a powerful concept but for WinForms, not VFP.
>>
>>Alex