>> I've been using FoxPro almost exclusively for 9 years. If I had to do
>> something that FoxPro couldn't do natively (well) then I was able to buy
>> a 3rd party library. For example a serial communications library.

I love ... no LOVE this VFP language ... I simply can't ignore the benefits of normalizing the functionality out of the MS languages and into a central framework. It just make too much sense.

>> Finally with ASP.NET, we have a RAD environment to make compiled web
>> applications using a graphical form builder. This certainly won't replace
>> FoxPro, but will most likey be the exclusive UI for all of my future
>> apps. Finally there was something FoxPro couldn't do, that I wanted to do.

I remember taking a preConference .NET seminar in Florida from a guy based out of Washingtion. He was proporting that ASP.NET (with C# and VB.NET implied) coupled with ADO.NET and SQL Server provided just about everyting one would need to develop a distributed application.

It takes me a while to catch on ... but I will eventually.

Nice to speak with you,

CT