Tracy

There have been discussions before about VFP being part of .Net - it isn't worth doing, as VFP would then just be VB.Net.

If VFP is your lifeline then pick up .Net too, then I suppose you will be prepared for whatever may come. That's what I am going to set out to achieve.

Kev

>Good point, however, around here the available jobs for VBers has continued to grow steadily and there is always a need--not true of VFPers.
>
>Also consider the wealth of new classes you could draw on as a VFP developer. All of those classes created in C# or VB you find on the web could now be used in your VFP apps if it were a part of .NET! Everytime I download an example in VB or C (so much is available and so many examples are online) I have to convert it to the VFP way before I can try to do the same thing. Not always easily done (or I am just too thick-headed and muddle-brained to do it quickly).
>
>Still, I'm not sure that is enough of a drawing point to justify VFP being a part of .NET (moot point now anyway/water under the bridge); I think the benefits of VFP outweighed the benefits of it being in . NET But it would have been great!
>
>Tracy
>
>>Tracey
>>
>>>That just SOLD .NET! Now, I was against VFP being in .NET for MANY reasons, but now I'm not so sure.....Think of the employment opportunities if it was...
>>
>>Opportunities will be more available jobs - depending on the amount of people who become proficient in .Net.
>>
>>Drawbacks will be less pay, less worth, becomes a common job and up against more competition - it all evens out as far as I'm concerned.
>>
>>But then I'm a miserable git!
>>
>>Kev