User gets "Cannot delete from table" with ASP/mdb app

[Bryan Russell]

I have an ASP app on the itranet with network users logging on with
their network credentials.

All the users have the same permissions to the folders as I do

The app works fine when I run it.

When another user tries it, the error says:

"Microsoft Jet database engine error 80004005 cannot delete form
specified table"

Any ideas for changes to my MDB or my queries?

Thanks,

Russell

[Ray at]

What permissions do they have? And are those permissions applied to the
parent directory of the .mdb file or just the .mdb file itself?

What does your delete query look like?

Ray at work

"Bryan Russell" <b_russ@yahoo.com> wrote in message
news:649e1033.0405131117.eec911c@posting.google.co m...

> I have an ASP app on the itranet with network users logging on with
> their network credentials.
>
> All the users have the same permissions to the folders as I do
>
> The app works fine when I run it.
>
> When another user tries it, the error says:
>
> "Microsoft Jet database engine error 80004005 cannot delete form
> specified table"
>
> Any ideas for changes to my MDB or my queries?
>
> Thanks,
>
> Russell

[Bryan Russell]

This is worth sharing: First I found out about and fixed the IUSR
permissions thing, next it was the Temp and Tmp folder permissions
(with only the dreaded "unspecified error" message to lead me), whew,
week later, its "permissions denied" for user accounts.

It turns out the question about the parent folder's permissions was
relevant.(Unless you did not mean "root" folder) I pinged a different
network admin for a second opinion (different to the admin who set up
my website). He quickly determined that the web site had two sets of
permissions enabled: "Shared" + NTFS as he described it. The shared
permissions presided over the folder-level NTFS permissions and
therefore the authentication would not pass the gateway (web root)
folder.

The only reason it was a problem was because the Access Database was
Linked to Excel tables inside the Website. (I know, it's hokey, don't
ask me why it is set up this way)

Anyway, apparently the way the Jet Database engine accesses the Linked
tables (when queried via Jet OLE connection) is based on the Root
folder Share permissions instead of the NTFS permissions. This is true
even though, under the same dual-permissions environment, an OLEdb
query to the same access database with a NON-LINKED table works just
fine. Weird.

The fix was to leave the NTFS permissions and remove the shared
permissions restrictions.


Russell


"Ray at <%=sLocation%> [MVP]" <myfirstname at lane34 dot com> wrote in message news:<#CdhXVSOEHA.2480@tk2msftngp13.phx.gbl>...

> What permissions do they have? And are those permissions applied to the
> parent directory of the .mdb file or just the .mdb file itself?
>
> What does your delete query look like?
>
> Ray at work
>
> "Bryan Russell" <b_russ@yahoo.com> wrote in message
> news:649e1033.0405131117.eec911c@posting.google.co m...

> > I have an ASP app on the itranet with network users logging on with
> > their network credentials.
> >
> > All the users have the same permissions to the folders as I do
> >
> > The app works fine when I run it.
> >
> > When another user tries it, the error says:
> >
> > "Microsoft Jet database engine error 80004005 cannot delete form
> > specified table"
> >
> > Any ideas for changes to my MDB or my queries?
> >
> > Thanks,
> >
> > Russell

[Ray at]

"Bryan Russell" <b_russ@yahoo.com> wrote in message
news:649e1033.0405141219.7d5fdcfa@posting.google.c om...

> This is worth sharing: First I found out about and fixed the IUSR
> permissions thing, next it was the Temp and Tmp folder permissions
> (with only the dreaded "unspecified error" message to lead me), whew,
> week later, its "permissions denied" for user accounts.

Using OLEDB (advised) instead of ODBC will typically eliminate that issue.
[url]http://www.connectionstrings.com/[/url]

> It turns out the question about the parent folder's permissions was
> relevant.(Unless you did not mean "root" folder) I pinged a different
> network admin for a second opinion (different to the admin who set up
> my website). He quickly determined that the web site had two sets of
> permissions enabled: "Shared" + NTFS as he described it. The shared
> permissions presided over the folder-level NTFS permissions and
> therefore the authentication would not pass the gateway (web root)
> folder.

Share permissions are irrelevant if you're accessing the file system
directly!

> The only reason it was a problem was because the Access Database was
> Linked to Excel tables inside the Website. (I know, it's hokey, don't
> ask me why it is set up this way)

Why is it setup that way? ;]

> Anyway, apparently the way the Jet Database engine accesses the Linked
> tables (when queried via Jet OLE connection) is based on the Root
> folder Share permissions instead of the NTFS permissions. This is true
> even though, under the same dual-permissions environment, an OLEdb
> query to the same access database with a NON-LINKED table works just
> fine. Weird.
>
> The fix was to leave the NTFS permissions and remove the shared
> permissions restrictions.

Unless your connection string was pointing to \\server\share\file.mdb, share
permissions should not have mattered at all... But, hey, I'm glad it's
working.

Ray at work