KevinBeaver   7610 pts.  |   Oct 6 2009  12:04PM GMT

Are you sure you want to spend money developing a front end for a backend database that might not scale very well? I’ve had several clients with Access DBs for their Web applications and have heard more moans and grunts than positive comments.

Nonitguy   15 pts.  |   Oct 6 2009  4:12PM GMT

I’ve been somewhat concerned about continuing to use Access as the database. However, I believe that the number of online users at any one point in time will not exceed say 5-10. Also, if necessary, I think the project could set up two or more Access databases to split the load and reduce “Access jams” and slowdowns. I’m all too familiar from previous experience with the problem of multiple users trying to use the same Access database at the same time. The project is intended to record data regarding affordable housing projects at two stages: pre-development and when placed in service. There are also data lookups and calculations involved. So, I think potentially we could have 3 separate databases: one with the lookups and calculations, one to hold the pre-development data and one to hold the placed-in-service data. Do you think I’m being delusional or overly optimistic?

mrdenny   46765 pts.  |   Oct 6 2009  8:03PM GMT

Sounds like you might want to move up to SQL Express from Access as Access may not be powerful enough for your project.