>Re: I can't help but get the feeling MS is basically saying to us "If you want local database access, use VB/Jet. If you want to go big, use MS SQL Server". Just my impression!

Absolutely not true. In fact, with what is coming down the pike - new version of ADO - and the ability for SQL/Server 7 to run in a non-windows environment - Win95/98 - Jet's days are numbered. Microsoft is trying very heard to be known as a data company. A lot of effort is going into both Universal Data Access and Data Warehousing - enough so that folks like Oracle and Sybase are beginning to get worried. In case you have not noticed - sales for those guys was pretty flat last year. All this said - no way MS tells people that DBF's and native VFP is the way to go. MS will lose a lot of credibility if they did. Sure, in a lot of cases - DBF's are fine. But in terms of MS, it only confuses the issue. Better to send one message. At least - this has been my take on things.



>Great, just when I've spent the last 2.75 years creating, modifying, and enhancing our system, I'm going to have to suggest switching to VB. I'll get started on that memo:


Well, there is ADO. Check out the thread on VFP being the best C/S front end. In your case, maybe VB as a front end to VFP middle tier COM Objects could be a good combination.