>Jos,
>
>>My concern with this product however is this: surely MS will enhance VFP9 to have a menu and toolbar system comparable to the other MS product lines. Is this so complex that it would not be warranted? If one purchases this product, which is not really expensive btw, invests the time and effort to implement it and then a SP for VFP comes out which handles this natively then it would be a bit of a waste of effort.
>>
>>If MS state that they will not be enhancing this aspect of VFP then this is a no-brainer decision. Perhaps KenL can offer a pointer here?
>
>My understanding (and my bet) is that MS will never update the VFP menu or toolbar system ever again. Period. Even on the long shot they might, I'm not willing to wait 2 years for this capability.
>
>The reason I build all my menus and toolbars in code vs. using the CommandBars builder is because I've always data driven my menu and toolbar definitions. This way a significant portion of my application structure is stored in a development tool independent meta data format that I can port to .NET, Delphi, or to a Linux based language if I need to do so in the future.
>

The 2 year argument is valid and is a good point to use this new tool.

A question - I run the sample form and got a good feel for what it is doing. When in the VFP IDE I run the form I try to issue a SET SYSMENU OFF and to put the commandbars menu system IN SCREEN. This works but the VFP system menu will not go away. Do you know why? How does one remove the VFP system menu and replace it with just the commandbars menu? My usual method of setting SYSMENU OFF and running my own VFP menu does not appear to work?.