How do I put the access database 1

[seaport]

I am going to set up an ASP application, which runs on an Internet Information Server on a Windows 2000 server. The backend database for the asp application is an Access 2000 database. I have two questions:

1. Where do I put the Access2000 database? Or say, where is the best place to put it? All I know is that I should not put it in the root directory of the web server.

2. How many concurrent users Access2000 can handle as a web database? I expect no more than 50 concurrent users. Is that OK?

Thanks in advance.

Seaport

 

[TechnicalAnalysis]

Apparently, you'll be lucky if Access can handle 20 users at the same time so....
Whereever you put your Access database is going to work as long as you have a right connection script. What you may need to consider is not to have it on a folder or path that browser can guess and download it via the browser.

Regards

http://www.technical.analysis.dingojunction.com

 

[Jonax]

...Which means that it should be outside

http://wwwroot...

Also: remember to permit the user IUSR_MachineName to write to it, if you want to update the data from your ASP-pages...

 

[link9]

Access might be able to handle a couple of folks accessing different records (tables) at the same time, although that's never been proven to me (I keep hearing it, though) -- but if two people try to access the same record at the same time... you're going to get an error.

If cost is an issue,

http://www.mysql.com

mySQL is free.

 

[Geee]

I run a site that has about 1000 hits per day. All the pages are generated off an Access database and it runs fine. The secret (well not really a secret) is to write extremely tight code. Only open a recordset at the last minute and close the recordset as soon as you have finished with it. Also remember to set you connections and recordsets to nothing when you have finished with them. To be honest, if you have it available, going to mySQL or MS SQL Server is the only way forward for anything but the most basic of sites.

G -GTM Solutions, Home of USITE-
-=

http://www.gtmsolutions.com=-

 

[link9]

And I would think that if you used a class or something to open those recordsets, first checking for errors, and then waiting if there is one, trying again, etc... you could fake it pretty well.

Sure was nice once I got my hands on SQL Server, though. Handles all of this mess beautifully so you don't have to.

 

[seaport]

Thanks for all your useful responses.

Seaport