Microsoft access too slow - update to what? Using Access FE/BE
Posted on 2004-11-09
We currently have a front end/back end Microsoft Access application. I have recently become IT amanager and have been looking into upgrading our system.
I am after some advice if possible...
The main back-end database is currently around 50 Meg, and is situated on our server, which runs on a 100Mn/s Ethernet network with switches.
The database has 52 tables, which i believe is too many for an access database?
Accessing the database using the front end, (which before i arrived was being run from the server as well via links from user desktops) is done from users PC's, with links to the tables in the backend.
The database is VERY VERY slow.
The main reason for looking into otherwise of providing this application to the clients.
1. I am pretty sure that several of the tables, such as 'constants', 'Days' and certain codes are just being used for list boxes - is this bad practice - wouldn't it be better just listing them in the required field?
2. Surely linking things just to display data is going to make obtaining information from queries that much faster?
3. I am looking at upgrading - which direction should i go? I was thinking of developing a web-based application, with client side files and access server database would that be faster than using the access forms to look at/change data?
4. I was thinking of using ASP.NET and VB.NET as an application base. would this be faster than other options such as PHP?
5. If we upgrade to a web app, would MS Access be a slow database to use - or should i go for MySQL (we can't afford SQL server) for a speed increase?
look forward to hearing your respnses,