>It's not neccessarily "better", just different. Think of it this way
>(the way Microsoft itself categorizes these products):
>
>Access is part of Microsoft Office, used by end-users.
>Visual FoxPro is part of Visual Studio, used by developers.

Exactly!!! The major problem with users though is conveying to them the benefits of an app written in VFP over Access. ie speed, robustness, feature, etc, etc. A lot of users ASSume that since M$ includes Access in Office that it must be the best choice. Generally speaking, if a user want to "develop" there own simple screens, reports. etc. -- use Access. If the user wants you to develop a system for them -- use VFP. And if they want access to files they've already created in Access -- ODBC. Been there -- debated that.
>
>
>
>
>
>I need a few good reasons why Visual FoxPro is better than MS Access.
>Can anyone help?