I'm glad to read that it isn't just me who thinks that VB6 (and prior) developers may be "in flux".

While I understand MS' wish for them to move to VB.NET, I don't think it would hurt MS' designs to formally suggest to VB6 developers that VFP is a good alternative for those more reticent to jump into .NET at this time. MS could, with little effort, produce a document outlining the differences to assist them too. Then they could sweep us all into .NET at the appointed time < s >

cheers



>Ibm Thinks so...
>http://www.theregus.com/content/3/26017.html
>
>Bob Lee
>
>
>
>>Tracy:
>>Besides the data-crunching do you prefer the VFP language over Pascal?
>>I still love the ease and clarity of the language - I mean scan..endscan is so beautiful ;)
>>
>>>We use both VFP and Delphi based on the requirements of the system. I think the job opportunities for Delphi programmers are better than for Foxpro developers in many metro areas. However, VFP is my preferred tool and if I can maintain employment using it, I will. I think that is why many consultants use it as their tool-because they have a choice and they can use it to provide the best possible solution for many business requirements because there is no IT shop mandating another tool's use instead. Borland has a demo version of Delphi you can download (or order the cd) and run to see if it is a viable alternative for you. I would check that out before making any moves in the Delphi direction. I would also look at the business needs in your area--what type of apps are typically in demand? What tools do the average IT departments of medium to large size corporations use? YOu can actually contact the IT Manager in businesses and find out what they see for their shop down the
>>>road. I think some research locally on the business-side is a good idea in addition to what you find out from other developers. Let's face it, nothing beats VFP for crunching data. That will probably hold true no matter what the developer-base of VFP is 3-5 years from now. But economic necessity may force you to change your primary development tool regardless. My advice is to use whatever free time you have to provide yourself with choices if your economic situation requires it. No matter what your tool of choice is, that is a good idea. Even C++ developers find themselves learning other languages when the employment options are not there locally for them too.
>>>
>>>Another note, I have already seen job opportunites for developers who are willing to learn .net and help the company move to a .net future. Keep in mind-no matter if you currently feel that .net is too new to invest in personally, if the job-base is there, it is a viable option for a developer that wants to keep their options open.
>>>
>>>Tracy
>>>
>>>>Lately I've been looking at Linux, just for fun now, but possibly with serious intent later. I notice that Borland's Delphi is cross platform capable. The prices are a little off putting for someone who just wants to play around ($999 for a new 'Professional' level user). What I notice even more though is the dearth of community outside of the borland site. I also notice that the metro search for Delphi returns even less than Foxpro. Yet, Borland has just announced a .Net compatible Delphi. I'm really drawn to the development suite idea, and Linux seems to be growing in popularity.
>>>>Just wondering if anyone out there has any ideas on this.
>>>>
>>>>Mike