Jess, I don't think that the name change from Pascal to Delphi made the difference, at least not the greatest difference. After all, they still advertise that it used "Object Pascal".

It was the marketing and most importantly the ground support that tipped the scale. However, maybe it's a good suggestion to make people realise that FoxPro has grown enough to be able to be seriously looked at again. Something like "Visual DataObjects" using "Object xBase" as the language might just make enough of a difference.

ANYONE OUT THERE AGREE WITH JESS ON THIS ONE? I do.

>>MS did a lot of damage with the marketing of FoxPro. Take a tip from Borland. Something very similar happened with Turbo Pascal in that it came out of favour. Then Borland released Delphi and begun a very agressive marketing campaign combined with sales offices intent on getting a copy in through the corporate door. They realised that once they could open their minds and see the product, they would like what they saw.>
>>But they had a problem. The argument always came up from others who were pushing their own favourite language that "wasn't Borland going under?" "No-ones using Delphi" and other rumours. Still Borland pushed on. Now it's being used as a serious development tool that is a serious contender in most corporations and businesses here.
>>
>
>DELPHI is just the new name of PASCAL in short, just as INPRISE formerly BORLAND. If MS decided to change the name FOXPRO to erase that "DEMISE" mindset, what would you suggest???
>
>Add to this if you have in mind:
>
>1. VISUAL DATAPRO
>2. VISUAL TAHOE
>3. VISUAL SPEEDPRO
>4. VISUAL DATAOBJECTS
>5. VISUAL FOXOBJECTS