Back Ends, Outgrow Access???

[redbull]

Hello, first of all I posted the specifics to this situation here


https://www.accessforums.net/queries...hen-26644.html
However, wanted to also find out what people would recommend...

I have 90 front end users, they all have this app with about 20 commands on it. Whenever a button is pressed, an insert query sends the entry to the Back end stored on a shared drive. My concern is While one users insert query is running, others would be locked out. ANYWAY, because of these concerns, should I consider an SQL back end? anyone ran into this kind of issue??

[pbaldy]

With 90 users, I would probably switch to SQL Server (or something else more robust). An Access back end can theoretically handle that many, but from what I've heard 90 is above its practical limit. You may be okay, depending on what the users are doing, but I'd at least start to think about switching over. There is a free version, though I haven't used it.

[Missinglinq]

You could continue using an Access Back End, and switch at a later date to SQL Server or Oracle, but given the current scope of your project, I think, like Paul, that the best approach would be to switch to an alternative, the sooner the better. Generally speaking, the larger the number of users accessing a database, the more important data security is, and almost any non-Access Back End will provide more security than Access will. And multiple-users accessing the data will be less problematic, as well.

Linq ;0)>

[redbull]

Thanks for the help and thoughts everyone. Being that I am new to a lot of this, up-sizing to SQL seems like a daunting task. BUT something I need to get exp in. I have plans of grandeur, Have the back end in SQL, and let the people who need it run reports off of a front page site or something along those lines... Easy to say these things... however Terrifying to attempt. Shit, I have only been doing VBA for 5 months now. So that's how shaky my world is lol.