[AccessD] Serving reports to the web

Doubtful.  On a web based application, the users hit the database and are
done pretty fast.  You'd be pushing the limit of a web server to have 3,500
simultaneous hits (within a few seconds).

Drew

-----Original Message-----
From: Josh McFarlane [mailto:darsant at gmail.com]
Sent: Thursday, December 22, 2005 7:30 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Serving reports to the web


On 12/22/05, Nick <nick at frasiervan.com> wrote:
> You will need a box to act as an IIS server on the network. Pretty much as
> Drew said. It does not need to be a server class machine, most modern
> desktops have enough horsepower for what you are likely to be doing.
Simple
> RAID should be safe enough. 3500 potential users isn't that much,
especially
> if it's unlikely for then to be requesting claims all at once. In any
case,
> if it does turn out to cause a problem, then you can easily upgrade the
> hardware with proven justification.

Careful. If you're interfacing 3500 users directly with an Access
backend, you'll likely hit a Jet maximum concurrent connection limit.

--
Josh McFarlane

"Peace cannot be kept by force. It can only be achieved by understanding."
-Albert Einstein
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com