I'm trying to connect my Dreamweaver site to an Access 2003 database via ASP. When I test the DSN connection on the test server, I get this error message:

[Microsoft][ODBC Driver Manager] The Microsoft Jet database engine cannot open the file '(unknown)'. It is already opened exclusively by anotehr user, or you need permission to view its data.

[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed

When we set up the DSN connection on the remote server, we pointed it to a .mdb file, which it's apparently not seeing.

My network manager swears its a problem with Dreamweaver, but I don't even know where to begin troubleshooting.

Can anyone help?

Could you post the connectionstring you are using? I suspect you need to use a UNC path but it's hard to troubleshoot given the tiny amount of info provided.

I have exactly the same problem, and have reduced the Access-2003 database to its simplest form, with a simple ASP page to display the table contents. I'm using Dreamweaver MX 2004, and have set full permissions for everyone, but it still doesn't work.

I don't think its an MDAC issue, as I'm using WinXPpro/SP2 which doesn't pemit use of MDAC (as its all apparently included).

I'm stumped!!

What does the Connection string say

also I could never get ASP (databaseing) and Dreamweaver working

I just write the code them test it in explorer as if live.
one thing I do is turn on IIS in XP use that as my testing computer

I have a OpenDB.inc

I have
<!--#include file="OpenDB.inc"-->
at the top of every page when I want to talk to the database

Then to write/get data I just do

SET RS = Server.CreateObject("ADODB.Recordset")

SQL =""
SQL = SQL &"SELECT Prod.*"
SQL = SQL &" FROM Prod "
SQL = SQL &" WHERE (((Prod.Sheet)='" & whereThis & "'))"
SQL = SQL &" ORDER BY Prod.Type;"

now let open it
RS.open SQL , connstring , adOpenStatic , adLockPessimistic

the HARDNEST thing to get right is the connection String write
that openDB.inc I wrote about 5 year ago and all i have to change now is the DBPATH and it works every time

as long as the database is in the same place as test / live everything should work.