Hi all,
I am trying to figure out what I am doing wrong. No matter what I try, I can not get past the following error.

OleDbException (0x80004005): The Microsoft Jet database engine cannot open the file It is already opened exclusively by another user, or you need permission to view its data.

Any help would be appreciated

Thanks,
Gary

Are you trying to test a page while you have the database open in Access?

Hi Planoie,

No, and this happens to SQL d-bases as well

Gary

Huh... now that IS odd.

I haven't worked with anything but MSSQL for the most part so anything else I say would just be a guess.

Are you connecting to SQL via JET?

No, String for SQL d-bases is as follows:
Provider=MSDASQL.1;Extended Properties="DBQ=C:\Senior Project\LibraryCentral.mdb;DefaultDir=C:\Senior Project;Driver={Microsoft Access Driver (*.mdb)};DriverId=25;FIL=MS Access;FILEDSN=C:\Program Files\Common Files\ODBC\Data Sources\LibraryCentral.dsn;MaxBufferSize=2048;MaxS canRows=8;PageTimeout=5;SafeTransactions=0;Threads =3;UID=admin;UserCommitSync=Yes;"
________________________________________________

Also... This only happens when I try and connect using a web form ... I can sucessfully attach when I am usinf a Windows form.

Thanks,
Gary

That connection string is pretty confusing. You are connecting to SQL? Where is the SQL information?

A standard .net connection string for use by the SqlClient.Connection object usually looks like this:
Data Source=servername;Initial Catalog=databasename;User Id=sa;Password=asdasd;
(http://www.connectionstrings.com)

It appears to be a permissions issue.

"or you need permission to view its data."

Do you see an .ldf or .ldb file in the same folder as the access database? This is the locking file which means some process or user has this file locked. If not, you shouldn't have any database problems, and maybe this is permissions then.

Also, you shouldn't have locking issues with locking unless you specify it in the query, specify it in a setting, or use Access to connect to SQL.

Hope this helps,

Brian

Thanks guys,

It does seem to be a permissions issue but I'm not sure what to do to correct this. Any Suggestions?

Thanks,
Gary

Either the ASPNET account or possibly whatever user permissions is specified directly in the database.