Hi Gordon,

In your message have a few incorrect propositions.

.Net front end is not strong roburst. It is very hard to create .Net apps over DBFs.

VFP do not need .Net, .Net need FoxPro and according Ken they will implement a few of VFP dataprocessing features in VB.Net. That was the reason MS VFP team next 2 year to try to rise interoperability between VFP and .Net.

Expectation of M$ owners are wrong about Access. Did you listen last 2-3 years any advertising that Access in a Database. M$ guys found that it is useless.

>It is my belief that both Visual FoxPro and .NET can exist together. Visual FoxPro offers a wonderful database for homes and small business. A strong robust, .NET front end application over this database is a nice combination for any hobbyist.
>
>This just goes back to the days when a simple database application like Visual FoxPro would be great for keeping logs of your record albums by musician, date and such. I remember when only Access would be expected to be used for the casual programmer. Now both Visual FoxPro, Access and Excel all kind of fall into that same simplistic programming realm.
>
>These are great stepping stones for eventually graduating to the full power of .NET programming, with powerful Oracle, SQL Server or even DB2 databases which are used at the corporate forefront of the commercial technologically challenging applications. With the up coming changes to SQL Server to take on some of the .NET feel to back end programming, the newer applications being developed will have more to return from the database other than just datasets; maybe custom collections!
>
>Hmmm I wonder when Microsoft will add Visual FoxPro script to the back end of SQL Server; maybe in SQL Server 2007.
>
>Oh did you say Visual FoxPro has a front end too!!! Wow a full package. Who needs .NET right. Did you say you WERE a contractor?