Maximum concurrent users

[JoeA2006]

I have developed an application that will need to support up to seven users
concurrently. The app is split into a frontend and back end. I am concerned
about the performance with that many users, but looking to the future, would
it be possible to push the data out to Sql server or Oracle and still use
Access as a front end if more users are added? I am not quite up to speed on
VB.net ( I do have some experience with VB6) This is a pretty complex app and
I would not want to have to build a front end from scratch. Is it possible to
keep Access as the front end in the possiblity of adding several more users?

 

[John Vinson]

I have developed an application that will need to support up to seven users
concurrently. The app is split into a frontend and back end. I am concerned
about the performance with that many users, but looking to the future, would
it be possible to push the data out to Sql server or Oracle and still use
Access as a front end if more users are added? I am not quite up to speed on
VB.net ( I do have some experience with VB6) This is a pretty complex app and
I would not want to have to build a front end from scratch. Is it possible to
keep Access as the front end in the possiblity of adding several more users?

Nominally Access will handle up to 255 users on the backend. In
practice 20-30 concurrent updating users is managable with a properly
designed split Access application (on a fast stable LAN).

Using a SQL backend with an Access frontend is eminently possible.
There's even a newish newsgroup microsoft.public.access.sqlupsizing
covering the subject. Your database may need some design changes; for
instance, if you have Forms bound to large tables, you may want to
modify the forms to be bound to queries which return one record (or a
small number of records) to move processing from the frontend to the
SQL engine. Often these changes will benefit a JET backend too.

John W. Vinson[MVP]