>
I didn't say it does have to be in VFP. Robert's message was in response to many comments and questions about why VFP was not specifically mentioned in the announcement and the subsequent revised web page. That would have been the perfect time to put the issue to rest if it was not still a possibility. His reasons for making the statement the way he did are not publicly known yet.
>

Why wasn't VFP mentioned in the announcement? Maybe because it is not a certainty that VFP will support this issue. Lets look at the facts, VB and VC will share the same IDE.. It would appear that many of these designers are integral to the common IDE. VFP will will not share the same IDE... Hmmm, I wonder what one could include from that..???

Why does everybody get so bent out of shape when VFP is not mentioned? Does it really impact your day to day business? And, if VB gets these nice features, instead of the knee-jerk reaction of 'When will it be in VFP?', why can't people instead say - 'Gee, maybe I should give VB 7 a serious look, and integrate those capabilities with VFP...'