Hi,
I'm a student looking for any recommendation to finding a solution to the following problem.

(Hope I'm posting in the correct 'section' of the forum, since my error says both IIS and ASP)

I'm running IIS on my WIndows XP Pro OS.
I'm connecting an Access database (.mdb file) to Dreamweaver CS4.
I've made the connection with the following string

"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Inetpub\wwwroot\mySite\mySite.mdb;"

When tested it shows as successful. If I add words, tables, images and simple html codes it works fine when tested and previewed through the web browser.

However, once I add a recordset/or query it produces the following error:-

HTTP 500.100 Internal Server Error- ASP Error IIS

Error Type:
Microsoft Jet database engine cannot open the file C:\Inetpub\wwwroot\mySite\mySite.mdb
It is already opened exclusively by another user or you need permission to view its data
/mySite/index.asp/line 9


Line 9 is where my recordset is when I view the code.
I've tried IUSR/Localmachine
I've tried to work with user permissions
Uninstalled and re-installed IIS
I seem to be getting no solution.

Any help rendered would be greatly appreciated.
Thank you :-)

Access is an odd choice for a web-facing database. Is that what your class requires, specifically? If not, don't use Access for this.

If you do need to use Access, I'd be inclined to think you've got a permissions issue. Make sure whatever user you're connecting as has NTFS permissions to the file/directory the .mdb lives in. In .NET you would need to assign permissions to whatever identity is set in the app pool. Classic ASP should default to whoever you have setup as the anonymous user in IIS, usually IUSR_MachineName or something like that.

Thanks a million!
Yes, Access is the requirement for the assignment.
I've tried the user permissions again.
Yes your recommendation of IUSR_MachineName is in fact the solution, it's working now.
Thanks again for your reply :-)

Glad to hear it worked! Tell your instructor that Teddy from the intarwebz thinks he shouldn't be teaching Access as an appropriate database for web based projects.