>>Is it possible to work with VFP and not be enthusiastic about it? <g>
>
>I don't know. They're all sayin "VB, VB, VB" or ".net, .net, .net" or "java, java, java".

From that point of view, I guess I work at a pretty cool company.. They just say, we can do this in VFP, we can do this in .NET. What would be wisdom? And we end up with a 2 month pilot project in .NET to check how it works, and whether it works for us or not.

If the pilot succeeds, we do it in .NET and if not, we do it in VFP. However, I guess I am about the biggest VFP supporter here (I pay for my own UT subscription, since they don't really think it's all that neccessary) and I'll always look at the VFP side of a situation, but at the same time I'm realistic and see that if we don't expand into the .NET territory (not me, but several others working here will) we're going to miss out on quite a part of the market.

>And they're all proud to do so. Whilst if I say "VFP" of "FoxPro", I get
>"VFP? Never heard" or "That still exists?" from clients.

Yes, I hear that too. They say 'oh, vfp is some kind of ancient language they used in the dos age' and I show them my personal application that I've built (and am building) in my free time and some COM stuff I've been doing for a client, and they kind of grow silent.

>And Other developers look at me the way people look, when You tell them
>Your favourite grandma just died - that "Ohh Frank, I'm so sorry - look,
>You could be so well off doing VB with SQL-Server and MTS.." <s>
>
>I feel sorry for them because they don't know better <g>. But that does
>not help the product.

I agree. And that is why I'll keep looking at new projects here from the VFP side, even if nobody else believes it is possible.
For my college-graduation project I'm going to build a VFP framework. The teachers there (all JAVA people) say it's nearly impossible in 6 months for 1 person, but I'll prove them wrong. <g>

Johan