I agree, I had not thought it through.

The name should end in .NET to be the same as the others in the family.

I think we should get away from using names ending with base so we can escape the heritage problems we have been having.

I quite like Db.net but even that harks back to dBase II days.

Visual Data.NET somewhat unfortunately becomes VD.NET which would raise a phew whoops from those who would put the product down.

If we call it VFP.NET then folks will still call it Foxpro (which in retrospect is a bit of a cheesey name) but I see no other option.








>>Thats an excellent idea Walter,
>>
>>my vote is for VISUAL XBASE
>>
>>
>>>Maybe, it should get a real new name, so that all IT managers can't draw the link to FoxPro and think this programming language is new. Since al lot of managers get real interested in new products, we might be able to get rid of the old 'VFP is dead' song, and finally get a bigger marketshare.
>>>
>
>IMO, it's a bad idea to mention xBase in the title of the product. Why not Visual NET.base or Base.NET ?