>Yeah, but using VFP with .NET at least makes it more interesting. If I can call an interop routine to vfp and accomplish something faster, more efficiently, and less expensively than a similar pure .NET developer, who do you think the client will prefer?

Good morning Claude;

The responsible developer knows what the best approach is. There are no absolutes but there can be real pain in some cases. When I cannot do something in VFP I use another tool. I cannot wait for Microsoft to come up with a fix or promise, which if implemented may not fully address the specific issue of interest.

If a developer knows the technologies and economics involved then his/her responsibility is to inform the client of the issues at hand. I do not like to look at a software development tool as if it was a “Left Hand Wrench” and make that one tool do everything. I am sure you know when to suggest and implement the best solution for your clients.

Tom