>>like I said in the conference yesterday it seems to me that with VFP3.0
>>MS finally decided to treat foxpro as a part of the MS family
>
>Ya. I also think there were soime dumb decisions being made, and they have been corrected (i.e. some execs got "managment adjusted")
>
>Also, if not VFP, who will compete with Delphi? Access? Ya right. Lets compare macros to a fast compiler (s)....
>
>>and I think we are starting to see that
>
>I hope so.
>
>Scot.
I'll be convinced when I'll see the ads in other magazines that the Foxpro Adviser.
Marc
If things have the tendency to go your way, do not worry. It won't last. Jules Renard.