«

Using ASP.net 1.1 and Microsoft Access.

I received the following error message. Why? I have closed the Access
file. I have another very small access file that opens with no trouble with
the same code, except a different name for the file.
The Microsoft Jet database engine cannot open the file
'C:\Inetpub\wwwroot\Accident.mdb'. It is already opened exclusively by
another user, or you need permission to view its data.

First - have you ever been able to open it before, through the web page?
If not - make sure the ASPNet user has 'Change' permissions on the folder
where the Access file resides.

--
David Wier
MVP/ASPInsider
http://aspnet101.com
http://iWritePro.com



"dancer" <> wrote in message
news:O$...
> Using ASP.net 1.1 and Microsoft Access.
>
> I received the following error message. Why? I have closed the Access
> file. I have another very small access file that opens with no trouble
> with the same code, except a different name for the file.
> The Microsoft Jet database engine cannot open the file
> 'C:\Inetpub\wwwroot\Accident.mdb'. It is already opened exclusively by
> another user, or you need permission to view its data.
>
>
>

How do I give 'change' permissions? And why didn't I have to give
persmissions on my other file?


"David Wier" <> wrote in message
news:...
> First - have you ever been able to open it before, through the web page?
> If not - make sure the ASPNet user has 'Change' permissions on the folder
> where the Access file resides.
>
> --
> David Wier
> MVP/ASPInsider
> http://aspnet101.com
> http://iWritePro.com
>
>
>
> "dancer" <> wrote in message
> news:O$...
>> Using ASP.net 1.1 and Microsoft Access.
>>
>> I received the following error message. Why? I have closed the Access
>> file. I have another very small access file that opens with no trouble
>> with the same code, except a different name for the file.
>> The Microsoft Jet database engine cannot open the file
>> 'C:\Inetpub\wwwroot\Accident.mdb'. It is already opened exclusively by
>> another user, or you need permission to view its data.
>>
>>
>>
>
>

Permissions, permissions permissions.

...

access needs to create a ldb file, which basically is a internal file which
says "userA is logged in" along with other stuff.
but the account which asp.net runs under MUST have permissions to the mdb
file, and to the directory to create/destroy this ldb file.



"dancer" <> wrote in message
news:...
> How do I give 'change' permissions? And why didn't I have to give
> persmissions on my other file?
>
>
> "David Wier" <> wrote in message
> news:...
> > First - have you ever been able to open it before, through the web page?
> > If not - make sure the ASPNet user has 'Change' permissions on the
folder
> > where the Access file resides.
> >
> > --
> > David Wier
> > MVP/ASPInsider
> > http://aspnet101.com
> > http://iWritePro.com
> >
> >
> >
> > "dancer" <> wrote in message
> > news:O$...
> >> Using ASP.net 1.1 and Microsoft Access.
> >>
> >> I received the following error message. Why? I have closed the Access
> >> file. I have another very small access file that opens with no trouble
> >> with the same code, except a different name for the file.
> >> The Microsoft Jet database engine cannot open the file
> >> 'C:\Inetpub\wwwroot\Accident.mdb'. It is already opened exclusively by
> >> another user, or you need permission to view its data.
> >>
> >>
> >>
> >
> >
>
>

"dancer" <> wrote in message
news:...

> How do I give 'change' permissions?

Right-click on the folder, click Properties, Security...

> And why didn't I have to give persmissions on my other file?

When using Jet databases you don't just need write permissions on the .mdb
file - you also need write permissions on the folder to allow the Jet engine
to create the locking database (*.ldb) file...


--
Mark Rae
ASP.NET MVP
http://www.markrae.net

"sloan" <> wrote in message
news:...

> access needs to create a ldb file

Just to maintain a certain level of accuracy here, Microsoft Access is not
actually involved in any of this process at any stage...

The OP says he's "Using ASP.net 1.1 and Microsoft Access" - clearly, this is
a web app so Microsoft Access isn't installed on the server (at least, I
hope it isn't!)

What we have here is a Jet database being interfaced through ADO.NET. When a
Jet database is opened for shared access, it is the Jet engine which tries
to create the locking (*.ldb) database.

The error message which the OP is getting: "The Microsoft Jet database
engine cannot open the file" is the key here.

It is the Jet engine, not Microsoft Access, which is trying to open the Jet
database, but it is unable to create the corresponding locking database due
to insufficient folder permissions, and so throws the error.

None of this has anything whatsoever to do with Microsoft Access...


--
Mark Rae
ASP.NET MVP
http://www.markrae.net

Good catch!

Thanks Mark.

However, I have found the error messages are sometimes a little "off" (not
in this case, but in general) with access errors.
Even the version of access might affect it I think.
I've run some Access97 tests, and get weirdo error messages when the
permissions aren't right.



"Mark Rae [MVP]" <> wrote in message
news:...
> "sloan" <> wrote in message
> news:...
>
> > access needs to create a ldb file
>
> Just to maintain a certain level of accuracy here, Microsoft Access is not
> actually involved in any of this process at any stage...
>
> The OP says he's "Using ASP.net 1.1 and Microsoft Access" - clearly, this
is
> a web app so Microsoft Access isn't installed on the server (at least, I
> hope it isn't!)
>
> What we have here is a Jet database being interfaced through ADO.NET. When
a
> Jet database is opened for shared access, it is the Jet engine which tries
> to create the locking (*.ldb) database.
>
> The error message which the OP is getting: "The Microsoft Jet database
> engine cannot open the file" is the key here.
>
> It is the Jet engine, not Microsoft Access, which is trying to open the
Jet
> database, but it is unable to create the corresponding locking database
due
> to insufficient folder permissions, and so throws the error.
>
> None of this has anything whatsoever to do with Microsoft Access...
>
>
> --
> Mark Rae
> ASP.NET MVP
> http://www.markrae.net
>

"sloan" <> wrote in message
news:...

> However, I have found the error messages are sometimes a little "off" (not
> in this case, but in general) with access errors.

*Access* errors...?

> Even the version of access might affect it I think.

Version of *Access*...?

> I've run some Access97 tests, and get weirdo error messages when the
> permissions aren't right.

You've installed Access 97 on your web server...???


--
Mark Rae
ASP.NET MVP
http://www.markrae.net

Access97 is a bit quirky for web access.
I'd consider upgrading the database to Access 2000 or Access 2003.

re:
!> You've installed Access 97 on your web server...???

I hope not.
Access itself isn't needed on the server. Just the database.




Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
======================================
"Mark Rae [MVP]" <> wrote in message news:ucyKi%...
> "sloan" <> wrote in message news:...
>
>> However, I have found the error messages are sometimes a little "off" (not
>> in this case, but in general) with access errors.
>
> *Access* errors...?
>
>> Even the version of access might affect it I think.
>
> Version of *Access*...?
>
>> I've run some Access97 tests, and get weirdo error messages when the
>> permissions aren't right.
>
> You've installed Access 97 on your web server...???

>
> --
> Mark Rae
> ASP.NET MVP
> http://www.markrae.net

"Juan T. Llibre" <> wrote in message
news:...

> Access97 is a bit quirky for web access.
> I'd consider upgrading the database to Access 2000 or Access 2003.

By which, of course, you mean that Jet 3.5 is a bit quirky for web access,
and you'd consider upgrading the database to Jet 4.0 (Access 2000, 2002 and
2003 all use the Jet 4.0 database by default)

> Access itself isn't needed on the server. Just the database.

Exactly - just the Jet database is needed on the server...


--
Mark Rae
ASP.NET MVP
http://www.markrae.net