PMFJI, but I received an e-mail from a friend at a former employer, a public health care IT company, that you all might find painfully familiar. I was asking about a product I created in VFP for the company and how it was doing. The sales were great but they are under the gun to port it to another platform.

A line from the e-mail: 'To quote (The C.E.O.), "I have never heard the words 'Enterprise Wide' and 'Foxpro' used in the same sentence." '

I can understand the desire to move to an SQL database but I think the perception is that you need to toss the whole thing out. CEO's accountable to share holders are perhaps scared to tell them their investment is tied to dBase (I am interpreting here).

Maybe it is time for M'soft to change the name from Visual FoxPro to Visual SomethingElse (insert your suggestions here) ala OLE to ActiveX.

Rick


>I'm taking graduate courses now and have an instructor in a database class whose only comment on FoxPro/VFP was that he didn't think it was around anymore. When I told him it was, his comment was that he couldn't understand why MS kept it. With no press, he doesn't see how it fits in with Access and SQL Server. The division I'm moving too also has that view.
>
>Scott Fitzgerald
>
>