>>Martin,
>>
>>I don't know if either is better than a well drafted document to foxwish. By "well drafted", I mean that the wish, to be the most effective, should include the business case for the wish. What does it allow us to do that we couldn't before? How does it make our work easier? I think answering those two questions in particular would be extraordinarily helpful to the foxteam. They wouldn't have to try to figure these things out for themselves. Further, citing one's own work and how it would be helpful gives them insight as to how people are using the product and could be the determining factor as to whether or not to investigate further.
>>
>>Unless one was intimately familiar with VFP's internals, or the change would obviously have little or no impact on them, I'd shy away from making statements or assumptions about the ease of implementation in the wish. The foxteam can easily determine that for themselves.
>
>Totally right. I will try to resume just some alternatives we see as workable that accomplish the task. As Mike said, the generated MPR could change to a simple CreateObject and some properties settings, without having to change the calling syntax. Of course, one could easily avoid them.
>
>As you say, I don't want to assume what's easier to do. I'll just stick to the alternatives I see as useful from a VFP developer perspective. But I think I'll post my suggestions here prior to write them to the FoxWish, so we all could discuss it a little and polish the specs.
>
>Thanks for your help, George.

Sure thing, Martin.

I think posting the wish here (and/or a document on Wiki) might be a good way to develop and polish the business case. However, people shouldn't look at it as if it were some sort of petition. If the wish isn't feasible, regardless of how many folks want it, it won't make it.