If VFP were a part of .NET, wouldn’t it need a new set of scripting command and it own set of tags. What difference does it make whether I as a VFP developer learn a new set of VFP Scripting command or I learn a new set of scripting command in some other language? I certainly have plenty of choices. Let me see, I can use C, C++, C#, J#, or VB. Is that about it if I want to be a strictly windows shop. Also, I could use perl, or Sun’s Java as a scripting language. These two can be easily adopted for use in Linux and UNIX in addition to running in windows. Microsoft has made VFP7 very capable of being a database provider much like MsSQL. VFP7 can be a provider via ADO OLE DB to an Access, VB, C or C++, etc front end. Doesn’t this mean I could use perl, with the proper ODBC DBI to access a VFP7 table using a client browser interface.

Also, Microsoft has written C# as a major refinement of its C++ language in answer to the Java threat. It is my understanding that many universities are replacing C++ with the Java language in teaching their computer science curriculum because it is a purer implementation of the OOP model with better memory management (e.g. garbage collection) than is C++. Microsoft will try to meet the Java threat by creating a better OOP, memory management, easier, friendlier and usable language in the form of C#. Also, it is my understanding the Microsoft will make C# open so it would be available for use in Linux and UNIX.

I will continue to use VFP as my primary language of choice. In the event that I need to learn some other language to implement a feature of Net, I will have to choose a second language. Since I don’t have a crystal ball, I can’t know which language to choose as a second language for .NET. I like perl because I’ve used it a lot in Linux, UNIX and Windows. C# would also be good. Any thoughts?

The opinions expressed here a strictly mine.

Leland.