>I don't know if this is entirely true, but Microsoft claims that the code remaining in VFP for backward compatability is less than 200K. As far as new menu and report design surfaces, I agree that they are sorely needed, but I'd think if they were coming that we'd have seen them in San Diego. As far as the menus go I'd actually rather see better OCX support so that we could use the coolbars control and some of the other ActiveX menu controls out there that don't work in VFP. IMO, VFP would be much better served in the long run if it can play nice with all of the various OCX's out there than rather then having new elements specifically for VFP developed.

Actually the main reason why VFP has problems with some ActiveX controls is because of how strictly VFP enforces the standards of ActiveX controls as opposed to VB. The trouble with this is most third-party ActiveX controls are tested on VB. I agree with the premise of what you are saying but what M$ needs to do is either reduce VFP's enforcement of the standards (not a good idea IMHO) or increase the enforcement of VB and the like so the actual so called standards are enforced across the board.

Cheers