>>Hey, before you knock Access, give it a try. I had never used Access until a few months ago, so I never had an opinion in the Access vs. VFP debate. I just knew I used VFP and it was a good enough tool that got the job done.
>>
>>Then I tried Access 97 in a little after hours contract. Of course there was a learning curve, but I was impressed with some features.
>>
>>Now I know it a little better.
>>
>>I hate it. It is an end-user database tool that is trying to be a development tool. It is weak.
>>
>>Now, on top of that, it is unreliable. I feel fortunate that I joined a company that uses VFP (well, FPD when I started). If MDM was using Access, I would have learned that and probably never looked at VFP. Sometimes you just get lucky.
>>
>>
>>>Check out the following link for a story on Access data corruptions:
>>>
>>>http://www.news.com/News/Item/0,4,25778,00.html
>>>
>>>No development tool is perfect, but I at least I feel confident in FoxPro's data engine. Does anyone think that MS will push VFP more as the premier Desktop/LAN database tool? ;)
>>>
>>>Jack Mendenhall
>>>Reinsurance Management, Inc.
>
>Are any commercial "shrink wrapped" off the shelf applications made in
>Access ?
>I dont think that microsoft recommends either visual foxpro or access for commerical applications ...

The simple fact that Access was for many years default data engine for VB implies that MS recommended it.