On Tue, 14 Jun 2005 15:43:25 GMT, AF <bscinc3000@Yahoo_NoSpam.com>
wrote:
Can I use Access to deliver web pages?
I can say something about this: for the last three years I have been
developing web interfaces to ms-access and sql server databases.
Mostly for our internal intranet - but also as a service provider to
outside clients.
To make a long,long story short, we pushed ms-access to its limits.
Conclusion?
Yes - you can use the Jet database MDB file (97,2000, whatever) as a
store for data and provide a HTML front-end for it in a web browser.
However, it requires A LOT of work and very careful server setup.
There are a lot of issues: Security, Connections, etc.
I've been using ASP for the last three years and am just now
transitioning to .NET. You have to know how to get your data and get
back out of the database as fast as possible. It's all about
connections to your database. It's true that you really don't want a
whole lot of people (less than 25) connecting to a jet mdb file at the
**same** time -- but that's the point: they don't access it at the
same time: they take turns. You design the web pages to make a quick
connection, get some data, and then disconnect.
We have hundred's connecting to one of our last remaining ms-access
db's (the rest have been up-sized to sql server). It's made up of 2
mdb files because of size limits with each db closing in on 1 gig in
size.
When I see someone ask whether you can use ms-access to serve web
pages I cringe inside === not because jet isn't a good database,
because it is. But because it requires knowledge and skill in setup of
the web site and the server that hosts it.
If you have to ask that question, you don't have that knowledge and
you have a long, long road ahead of you.
In many ways, sql server is much, much easier. Now that we are finally
almost moved over to sql server, it's so much better I can hardly
believe it.