• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 178
  • Last Modified:

problem driving MS-Access via ASPs

Not exactly a CGI question, but there's no category here for ASPs, so here goes...

I developed an MS Access v7 DB on my laptop (Win 95) and I'm able to access it from PWS with ASP pages generated by the FrontPage98 database wizard (through ODBC).  I can also reach it from ASP pages I hand-coded.

When I moved all of this to Windows NT 4.0/IIS 3.0 I got problems.  Even though I've added the DSN entry for the database, the ASP is called and never returns (locking-up IIS).  Access v7 is installed on the server.

Is there something extra I need to do with security or accounts for this to work?

That's the only thing I can think of which is added/new with NT.  I can run other ASPs (non-DB) on both systems.  The Web pages haven't changed and the DSN entry is the same.

Any ideas/thoughts would be very much appreciated.
Gene Klamerus
Gene Klamerus
1 Solution
I believe that your access DB must be accessible by the Web Server, or at least the DSN.  Did you set up the DSN as a "System DSN"?  It must be for the web server to access it.  Did you test the access when you created the DSN?  Also make sure that you supply the correct Username and Password info in you connect info ""DSN=xxxx;UID=xxxx;PWD=xxxx;DATABASE=xxxx;"
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now