Access with Internet

[Jeff]

Hello,

I designed a small Access Database (version 2000) for a Dept in a large
company.
Usually only 3-4 users are using it.

Now they are asking for other employees to be able to update information in
the database. The problem is they have 600 employees.

I know Access has a limit of 255 concurrent users & I am sure if more than
even 50 were trying to update info Access would get really slow.

So now I am trying to find an alternate solution.

The info that the other 600 would have to update is small, only a few fields
in 1 Table.

I was researching about possibly using Data Access Pages, where they can
update info over the web rather than through an Access Front End. I have
never worked with Data Access Pages before. So...

Is their a limit to the number of users that can be on the database with
Data Access Pages ?

Would their be a great decrease in performance if a lot of users are on at
the same time ?

Any other options I would have to do what I ask ?

I guess moving over to SQL server, which I don't know is a possible option
for them.

Any help would be greatly appreciated.

Thank you,
Jeff

 

[NetworkTrade]

You need to determine the probability/statistics of useage. Is it 600 all
signing in at the beginning of the day? meaning high probability of
exceeding simultaneous maximum.....or is it 600 that could/might use it
sometime during one week and at any time during the business day? meaning
very low probability of hitting maximum simultaneous..

that's your first part. Even though 600 is alot - it could be that the
probability of 25 being in the application at the exact same time might be
actually quite small given that the real time in the application may be just
a minute or less..... on the other hand if it is a time card application
everybody does at the exact same time - no way...

a small set of data that you mention can be very easily made up in vb for
the front end of a web site...

the back end can start out as Access - - and could move/change to sql if
Access proves not up to the simultaneous activities without redoing that
front end...