Re: Using .Connect to relink fails! Really need help with this!
From: TC (no_at_email.here)
Date: 08/10/04
- Next message: kiln: "Re: Using .Connect to relink fails! Really need help with this!"
- Previous message: MTennant: "Re: Locked database prohibits changing security"
- In reply to: kiln: "Using .Connect to relink fails! Really need help with this!"
- Next in thread: kiln: "Re: Using .Connect to relink fails! Really need help with this!"
- Reply: kiln: "Re: Using .Connect to relink fails! Really need help with this!"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 10 Aug 2004 11:45:15 +0930
I suggest you show your actual lines of code. Lots can happen between the
code as written in a document (eg. the secfaq), & as implemented by specific
programmers!
When you say the front end grants all users all permissions on all "tables",
I assume you mean on all *links*? If so, then, I can't see why a user
wouldn't be able to delete those links, regardless of what permissions he
had (or did not have) on the linked-to tables.
HTH,
TC
"kiln" <kiln@brick-like.com> wrote in message
news:MPG.1b818ab293d827d79898af@msnews.microsoft.com...
> I'm stymied by an apparent permissions issue. I'm using the code in the
> SecFaq, item 14.3, with a secured Access 2000 sp3 db.
>
> Backend has all table perms revoked for all but admin users. Queries are
> used by reg users at the front end to gain access to data (via forms,
> rwop, etc). Well there is one table that all users have full persm to.
>
> The front end grants all users all perms on all tables.
>
> The code in 14.3 is supposed to delete each linked table and then relink
> to it using the values passed in. As soon as I'm running as a ordinary
> user (not User, rather a member of one of the custom groups that have
> limited perms) each line of the .connect relink routine errors out -
> Error 3012 (Object '|' already exists) for the single table that all
> users have full rights to and Error 3110 (Could not read definitions; no
> read definitions permission for table or query '|') for all the rest.
>
> The first error must indicate that the one all perms ok table link
> wasn't deleted like the routine is supposed to do.
>
> The second error I'm not sure what the issue is. Using .connect is
> supposed to obviate the perms issue but here it is
>
> I've spent lot of time on this and have to solve is soon, so I hope
> someone can point me to the problem. I'm sure the technique works but I
> must be misapplying it.
- Next message: kiln: "Re: Using .Connect to relink fails! Really need help with this!"
- Previous message: MTennant: "Re: Locked database prohibits changing security"
- In reply to: kiln: "Using .Connect to relink fails! Really need help with this!"
- Next in thread: kiln: "Re: Using .Connect to relink fails! Really need help with this!"
- Reply: kiln: "Re: Using .Connect to relink fails! Really need help with this!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|