I guess I just found it amusing that you considered their development or planned delivery/sale method used to be an "oldster mindset" when some would consider holding on to a known end of life cycle product like VFP in any of its incarnations including the open source additions to be an example of the "oldster mindset." It won't be that much longer until VFP9 is not even available for purchase... Can you still purchase it from MSFT or is it only available now from retailers who still have some in stock? Is MSFT still packaging it? I'm not saying it isn't a great tool and serves a purpose, just that it isn't one of the "younger products" and not typically used by a "young mindset" so I found your comments referring to the other developers working on a commercial product to fall into the "oldster mindset" category simply because it was "commercial" amusing. :o)


>Not sure what you're asking. I'm almost positive all of them were meant to be commercial products, no? I'm not saying they were literally or necessarily oldsters but that it is an "oldster mindset" to make such products commercial IMO.
>
>>>Really? All of them? Do you have any evidence to support that opinion (only referring to the above statement)?
>
>>>The problem with these guys is they have the oldster mindset of charging for everything and being unhappy that it's not paying for itself.
>>I think it's a no-brainer at this point that such a solution needs to be Open Source, not a proprietary product controlled by a small group of people. The more you get the community involved the more a product will have a life of its own. Regarding VFP, look at what's going on at CodePlex. I predict many of these solutions will come out of there..
>>
>>>That would be great to see, but they don't always mature. Whatever happened to:
>>
>>.>NET Extender for VFP
>>>VFPCompiler for .NET
>>>or
>>>VFP Studio
>>