I'm in to agreement. The Foxpro is at least recognized by many. Microsoft must educate the masses about Visual Foxpro and all it can do.



>Renaming the product will not help. Then it will just be "oh.. that's the program they used to call FoxPro"
>
>
>>I've been using Foxpro since it was Foxbase+ and believe it can do 99% of what I ask or want it to do. It just has a name "Foxpro", that has come to symbolize (to some at least)a product that is not robust or professional enough for project development. I believe its time for MS to rename Visual Foxpro and give it a name that more accurately reflects what it is today.