>>For some of us there is no such thing as "VFP work", just products or >>services we sell. Those products could be written in Delphi, VB, VFP or >>whatever.

That sounds good! Let your work speak for itself. I've always subscribed to that philosphy. I'm the only VFP person on a team of all Powerbuilder people. I was hired 4 years ago to support some legacy apps and now I've rewritten them all in VFP and nothing but new developement work ever since. They don't like it, but they let me have my way because I've brought in alot of business. Countless number of times they have expressed concerns over who will support this stuff if I leave. Now, I almost feel I couldn't leave if I wanted. I would be letting alot of good customers down. This is what I mean. VFP, thanks to MS, is now precieved by the market as a out of favor technolgy.

>>The clients sometimes show interest in the tool but it is the product and >>above all *the firm* they pay heed to.
Customers are getting smarter. They need to feel comfortable about the tools your using and the availability of talent. VFP is now seen by the marketplace as kind of a rogue.

>>I agree about looking ahead. But not too far.
MS is betting the farm on this NET stuff, I'm taking it very serious.

>>Putting market aside: I've looked at NET and I'm waiting for somebody to tell me a *technical* reason why (for example) a West Wind user should seriously contemplate abandoning all that to make the move to a CLR-compliant tool just to get the CLR.

You probaly won't find one and West Wind probaly scales better, but its still the FoxPro.

I'm not making any decisions. I'm happy doing VFP and my customers like what I've done for them. I'm just being proactive.

Regards,
Charlie