>>>>Ok Tracy explained that. Au-contre to what you might think, I am not negative on NET itself. I love cool new stuff like
>>>>any other geek. It is usually attitudes that gets me barking {g}
>>>
>>>How is that possibe? You haven't had any motivation to try it out? I was learning .net 1.1 while making my living on FoxPro. Now that has shifted and I won't be looking backwards.
>>
>>When net 1.1 was out I was in the midst of battle against the time and dying unix server. We went through full on-the fly conversion of multi-application suite from Unix 4gl platform, to VFP/windows which we completed in 2004 (hence me being slightly pi$$ed with 'the vendor'!). Anything but VFP would have broken our neck.
>>By nature of my job I cannot take any risks. I have no choice but to be late adopter; but once/If I get there (NET), rest assured I will find my way arround ! ;)
>
>I don't understand the "take any risks" comment. Can you explain how going to .NET would be taking a risk?

Now maybe not that much of a risc (just bigger bill) , but back in 2001 ?

When you have preassure of converting entire suite of applications (5-6 modules) that are infact backbone of organisation,
then you are bound to use tool what you are comfourtable with, and where presumably there would be no surprises down the road.
( Fox seemed very healthy back then with versions comming one after the other...)

I did not even choose FoxPro in this case, (Although I would choose it readily even today!) but just took off where my predecessor left it. Thank's to VFP flexibility / RAD we completed everything on time. Bear in mind that during of whole period of painstaking conversion, application did not stop functioning EVER. Modules were developed and deployed, replacing old ones on the fly.

Had I played NET messiah back then, and failed to complete on time, we would have ended up in dissaster.
Put yourself (or better earn yourself) my position, and you would perhaps understand what I am talking about.

Cheers :)