>John, Fred,
>
>>I've heard that the positioning of Access is going to be more as a front end for SQL as opposed to a standalone >product; not that it cannot function as such.
>
>>I think anything and everything is going to point towards SQL as a matter of policy within MSFT, including VFP.
>
>>Just my opinion...
>
>
>This may be a dumb question but if your opinion is correct, does this mean that V-Foxpro will eventually loose it's native database and tables?

Andy,

Hmm.. I've often thought that MSFT would be smart to separate the data engines from the front ends but with COM, DCOM & COM+ providing non-ui data-based functionality PLUS the awful mess you'd have trying to separate those pieces in VFP I don't think what you're suggesting will happen. Still, I like the idea and in a perfect world that's what I'd like to see.

Essentially we have that now. You can have a SQL backend, a VFP or VB COM (or Delphi, etc) middle tier and a web, VFP, VB, HTML etc front end.

As an aside... I think that MSFT might be holding off on the object menus and reports until they get a single menu or report object that would work for all products. Personally I think that would be smart - thinking of their produces as components made up of components.

Best,

DD