>DD,
>
>>Robert Abram, who lives here in UT, has already figured out how it can be done. He's actually sent me some very preliminary code and you can do things like put a menu in a form, etc...
>
>From what I know of Robert, it doesn't surprise me in the least and I'll bet it's cool.
>
>>Things is is that VFP needs to play better in MSFT's sandbox and (IMO) MSFT needs to make those object menus the same (underneath) for ALL MSFT products. Doesn't make sense to me any other way.
>>
>
>Doug, I agree with this. I must admit I first mis-read your statement. If I were to hazard a WAG here, I'd bet that VFP menus (internal to the application) are already exactly the same as C++ and VB's. IOW, resources. The only difference in the three would be how they're stored in a project for the language.
>
>There's one thing that concerns me here, however. One of the things I've always done is hacked the scx, frx, pjx, mnx, etc., etc. files Of course, the project object kind of eliminates the need, but the rest remain. For example, look at what John Koziol did with FRX2Word. I don't know if I should even be concerned about it, but something in me tells me that if we lost that ability, it might not necessarily be a good thing. Then again...I could be wrong.

George,

No doubt there'll be tradeoffs. (To know how I think about Solutions v Tradeoffs read Thomas Sowell's tome, "The Vision of The Annointed", which IMO is brilliant.)

Still, reports and menus have been suspiciously untouched over the last several years and m'thinks there's a game afoot.... <g>

Best,

DD