>I just spoke with someone at Microsoft Support regarding a problem with the VFP7 OLEDB provider and ADOX (I was in the VB Data Support Area believe it or not). The guy on the other end of the phone kept calling what I was doing "FoxPro", no matter how many times I said I was doing "Visual FoxPro". This guy was/is sharp and helpful, but seemed to have it in his head that I was doing "old Fox" stuff.
>
>
>To me, FoxPro is a 1980's/1990's product geared towards single-user work with not a lot of flexibility and a pretty poor interface. Visual FoxPro 7 isn't FoxPro any more than Visual Basic 6 is BASICA.
>
>
>What do you kids think?

Steve;

Visual FoxPro is a pleasure to use. We did things with FoxBase (1985) that were unreal. We had multi user at about that time. I have an original copy of FoxBase Lan in shrink wrap - not yet opened! I also had real clients who used foxbase and fospro in a multiuser environment. It worked but not with the ease we have today.

Remember the connectivity Kit? Such fun!

When VFP 3.0 cameout I promised not to look back. We did a lot with the older versions - yes but it was bandage time all too often. Now it takes less time and is easier to use VFP to create a professional application.

Key Levy's Genscreenx helped foxpro to have a much better interface. A lot of people helped to make foxbase and foxpro a professional product.

Looking back is not an option. Give me the "Visual Fox" any day!

Tom