can you use access with asp.net safely?

Question

i'm currently using asp.net(with vb code behind)
and an access database (since sql server and mysql both start giving installation errors)
but i've heard that there are problems with access and multiple connections

since it is one web server accessing the database does it count as one connection or does it count as 1 connection for each user connected to the website

there are about 6 people in the company which can access the website

will there be issues with access or should i find something else

Answer 1

Well from your description of your current structure it could serve its purpose for a period of time but beware performance will be impacted as your company grows and records grow. It totally depends on the type of interaction with the database your site is doing ie whether your using as a read only pulling data from it or both transaction entering/manipulating data and reading it as well.



If database is on the web server then as soon as a asp page is called with a open database command will count as 1 user in it, again I wouldn't be too concerned with opening initial connections as you mention you have only 6 whats more important what your doing after the connection is made querying large amounts of data or inserting to multi tables and many fields simultaneously is what loads and taxes the db.



Also make sure you close and dispose any open connections and recordsets once page or purpose is rendered this can cause serious issues in performance and errors.

Another important consideration is whether you will be executing your SQL through your web pages or through the access database or both just keep in mind that if you do it through the access db then when you need to change or create a new query you have to bring the database down from the webserver and do your change or adds and bring it back up so there will be a period of inoperablity for the users.

Answer 2

for only 6 people using it i really doubt it will give you problems - i think access can serve quite a lot of requests, i would say well into the hundreds, maybe the thousands, though i've never tried it.



i would still recommend sql though if you can. it's really no different from access in a programming sense, and though a lot more expensive, is guaranteed to work.

Answer 3

The problem with access is that when the record is huge it will slowdown

Answer 4

The above answer is ideal on, yet your e book is faulty on the region of aspnet_regiis.exe. this is got here across the following: C:WINDOWSMicrosoft.NETFrameworkaspnet_regiis.exe