Go to the MS site. Find a bunch of pages that demonstrate that VFP is a developer's tool. Then find a bunch of pages that demonstrate that Access is meant for end users that might want to dabble in programming a bit.

The pages are there. The fact is that Access is in MS Office. VFP is in Visual Studio.

Maybe Access is the best tool for what you are doing. Maybe some end users want more contol over reporting, etc. But, it is also possible that VFP is the best tool. Depends on your situation. The MS site will provide a lot of information for the decision. If you have a fair bit of data over a LAN, I think a simple demostration of Access might help...

Look at it this way: If you go to Access, you will have a good excuse why you aren't getting too much done...

Joe


>The company I am working for is mulling replacing VFP with Access (yikes!). I am sure most of you would agree from a professional development stadpoint, this would be a disaster (and probably drive me to a new job). I want to know if there is any sort of articles out there that compair the features of the two to help me make my point that it would be a huge mistake to make such a change. Thanks!
>
>-Matt