There are two different issues here, and you have them intermingled (most people do that). The first is the data store. Access is NOT a data store. Traditionally, it has used Jet for data storage. Jet is not a good storage place. It does not scale. The second issue is the UI and reporting tool. This is where Access really falls...and it is not that great. If you need something quick and easy, use Access, which can connect to SQL Server. If you want a real developer tool, use VFP.

BTW, I'm up here at the MVP Summit at Microsoft. John Koziol pointed out this construction site here on the MS Campus. It shows the future of Access. The picture is here: http://leafe.com/personal/mvpsummit03/accessfuture.jpg/view


>It's been quite a while since I looked at Access and was hoping for some insight as to whether the old VFP is better than Access arguements hold up. i.e. Access more for smaller apps, VFP handles data faster and larger amounts, Access performance drops off as users and/or data size increases, etc.
>
>I have a potential client that has one Access app. Their company (users, money data,etc) has increased by over 5 times. I am suggesting future development be VFP or VFP/SQLServer based, which could access the existing Access data if needed, but they hope to continue with Access because they already have an app in Access.
>
>Confirmation to the above and any other reasons/arguements greatly appreciated.