>>For a big project, with client/server functionnality, I need to present why Access is not adapted and why VFP 5.0 is better.
>
>Since this application will be used in several countries, you will have a big advantage at first by plugging INT'L Toolkit in it. This is a terrific tool done by Steven Black. You can post a message here in the appropriate category to obtain more information from Steve.
>
>Also, Visual FoxPro is a full OOP environment which I don't think Access is. However, I don't know Access so I can't be sure on this one.
>
>But, I have the feeling this is gonna be a long thread and you'll get all the information you need.
>
>BTW, Rushmore is in Access now, so where's the power coming from? :)
>
>IMHO, there shouldn't be any comparaison between Access and Visual FoxPro because those products are focusing on two different markets and each one as its own use. As for your product, there is no question, Visual FoxPro is the way to go.


The Access engine, even 97, is still slower and the MDB is not as stable as VFP's DBC. If the MDB get corrupted, it's a lot more difficult to recover.

Access is almost entirely Visual, so from a programming standpoint, you lose functionality by having to work with lots of constraints.

And lastly, to restate what Michel said, Access was designed for ease of programming, not speed or efficiency. If this app is going to be as big as you say it is, Access cannot cut it. (Some would argue that you can tie Access to VB, and that's a good argument. I don't really have the ammunition to fight that one. Perhaps someone else does...)