MS Access Limitations

  • Thread starter Thread starter Keith
  • Start date Start date
K

Keith

First off.....Im a novice.

I am having a website designed using ASP.Net with MS
Access DB. It has come to my attention that MS Access may
have severe limitations with handling multiple concurrent
users. Could someone please define the following:

1. Limitations of MS Access handling multiple concurrent
users?
2. Is MS Access truly compatible with ASP.net?
3. Alternate Database to use with ASP.net?

Please advise.....thanks.
 
Keith,

Responses inline below.

Gary Miller
Sisters, OR
1. Limitations of MS Access handling multiple concurrent
users?
Click to expand...

Microsoft says 10, I believe, although it all depends on
what the users are doing. If they are only viewing data
generated by an asp page, you could probably have quite a
few more with no problems. The number goes down with the
increase of Adds and Edits that are happening in the same
place. If Access is just offering up views of data, there
isn't near the overhead being used.

I use Access with a lot of Cold Fusion and ASP sites with no
problems, however none of the sites is in the thousand user
an hour category.

Keep in mind that Access only has to work when it actually
gets a command from an ASP page. When the visitor is reading
a page or filling out a form there is no activity until they
call another data page or hit a submit button.

2. Is MS Access truly compatible with ASP.net?
Click to expand...

That is more of a function of ASP.Net which should be
compatible with about anything. ASP.net is using ADO which
Access loves.
3. Alternate Database to use with ASP.net?
Click to expand...

MySQL or SQLServer would both handle a lot more users with
less record locking problems. I don't know about MySQL with
ASP.net though.
 
Back
Top