>>>Where I work, stupid M.I.S management ask us to justify the use of FoxPro over Access.
>>
>>You took a change by putting "stupid" in front of "M.I.S.". :) What if they log in?
>>
>>>Can you help me start the top 10 reasons not to use Access over Visual FoxPro!
>>
>>Reason #1: There is no need to compare a professional development l.
>>...
>>Reason #10: There is no need to compare a professional development tool vs an end user tool.
>>
>Yes you are right. But the stupid ... do not care.
>
>I need good technical reasions. Hard stuff.

Fox always has been and will be for a while the fastest database
engine...

Database corruption in Access is a misfortune that very rarely can be
corrected. Fox is flexible enough to allow you to copy data somewhere
else before you completely lose access to it. If worse come worse, -
there is always a shareware FixIt for DBF tables.

Also, Fox allows you to have loose tables, free tables as they call them
now...

Fox's memo fields are more reliable than those of Access...

...But...Access is part of MS Office. Did you see Office 95 package???
I got a copy (illegal :) and played with. Man, it's awsome!!! VB melts
into it so gracefully, that I got carried away playing with the entire
thing like a little kid :)