Access _can_ work as a back-end for public
searching online, using Active Server Pages (.asp's) but only if the servers on
which it resides qualify. It needs IIS 3.0 or better, which only runs on
NT Server 4 and Windows 2000 Server. So if your institution hosts websites
using, say Apache or Linux/Unix server software, you'd be out of luck, even if
your client systems use Access to design your database. Another disadvantage is
the problem that, if you create your database in Access 2000, and the server has
ODBC drivers for Access 97 or another version, your hard work won't fly on the
server...
There are some converters available, but I can't
vouch for the reliability and functionality of them. The solution, as someone
mentioned, is to build something in SQL...or perhaps you can design in Access
and convert to SQL.
Good luck. I'm interested in how this turns
out myself.
---------------------------------
Jason T. Larson Special Collections Librarian and College Archivist Henry Whittemore Library Framingham State College 100 State Street PO Box 9101 Framingham, MA 01701-9101 |