Using Access in web app?

[JED]

I have an opportunity to work on a web based project using Access. However,
there has been a suggestion that MySQL might be a better alternative. The
project is actually a small project (less than 4000 table rows) and I feel
Access would work well. I lean toward using Access since there is a current
offline Access application related to this project. I feel that keeping the
underlying software similar makes for easier interaction between the two.
Dream Weaver will probably be used to generate ASP web pages. I have found an
ISP who can host an Access database. How practical is it to use Access as a
back-end database in a web app? Does Microsoft approve of using Access in a
web app? Can Access hold its own in this situation? What problems can I
expect? Can Access be made secure?

 

[dlbjr]

It'll do fine for a small web system. But, remember no system stays small, they all keep growing!

'dlbjr
'Pleading sagacious indoctrination!

 

[Bullschmidt]

I love Access for non-high traffic sites. And yes the database could be
the same as the desktop database but the Web pages would of course just
be using the tables. For example if the Web pages read data from the
database then one could FTP the latest database up anytime one wanted.

And if the site writes data then it is easy to back up the Web site data
just by FTP downloading the one Access .mdb file.

If the site gets very slow or the DB gets corrupted then consider
upgrading the database to something more industrial-strength like MySQL.

Best regards,
J. Paul Schmidt, Freelance ASP Web Developer
http://www.Bullschmidt.com
ASP Design Tips, ASP Web Database Demo, Free ASP Bar Chart Tool...