ASP + Access database

  • Thread starter Thread starter hk_guy
  • Start date Start date
H

hk_guy

I would like to do a Web survey using ASP 3.0 plus access database. Since
the number of users may be over 1000, I am affraid that whethter it could
handle the concurrent update well. I have the following concerns. whould you
help me to clarify them:

1. whether ASP control the concurrent update on Access by itself?
2. if TOO many users connect to my web survey page and click "submit" the
result, Could ASP handle ALL the results at the same time and could not
cause some users' data lost?

Actually, I think the time-slot used by ASP to update the access database is
very short but I wanna to prevent the crash on the database when
concurrently updating


Thanks a lot for your kindly help
 
MS does not recommend use of Access (Jet) database with IIS.

By default, IIS is not compatible with multi-threaded
applications like the Jet database engine.

There will be a failure if Jet tries to create a new thread
while IIS is trying to create a new thread.

To avoid this, you need to force either Jet or IIS to
use only a single thread for data handling.


For example you can try setting

HKLM\software\Microsoft\jet\4.0\engines\jet 4.0\threads
to 1 instead of 3 on the server.

But access/jet databases are tricky to maintain and support
on a webserver, so generally we just recommend using sql
server or something else if you are expecting a heavy
load.

(david)
 
Thanks for your reply

If I use SQL server instead of Access, I just need to implement the coding
as usual as implement it in "ASP + access"
No need to concern the concurrent updating or adding an entry to the
database by ASP. It will be controlled by "ASP + SQL" by itself. is it
correct?

P.s my online web ASP survey pages should include 1000+ users to submit
data. I think access may not be suitable as your words

thanks
 
hk_guy said:
Thanks for your reply

If I use SQL server instead of Access, I just need to implement the coding
as usual as implement it in "ASP + access"
No need to concern the concurrent updating or adding an entry to the
database by ASP. It will be controlled by "ASP + SQL" by itself. is it
correct?

Yes. You just have to change the connection string to connect to a different
database. But you have to have a SQL database running on a server.

P.s my online web ASP survey pages should include 1000+ users to submit
data. I think access may not be suitable as your words

thanks

Using Access, you need to take the page off-line to backup or compact the
database. Access works ok if that doesn't matter. Normally this is more of a
problem than the threading issue.

(david)
 
I got the direction how to do after your words
Really thanks a lot for your kindly explanation
 
Back
Top