Users have dbSecFullAccess but can't read connect string   

Hello Everyone

Using Access 97 and a split db. The problem is sorted, but I wonder if
anyone can tell me why it may have happened so I can avoid it in the
future.

Users with dbSecFullAccess on the tables container can't read the
connect string if the tables have been previously linked by another
user. The connect string for the second user is "<unknown>" without
the quotes.

What happened to dbSecFullAccess on the tables container, or more
precisely, what did I do to corrupt it?

Info:

BE mdb on server, FE mde on local PC's. Both databases are secured
using a devel.mdw and the company uses a site.mdw.

If I'm creating a lot of new queries or changing the BE tables, I
delete the linked tables and toggle permission for the tables
container between dbSecFullAccess and dbSecNoAccess. The tables are
linked and group permission for the new queries is applied.  Would
this toggling for linked tables invite the problem?

If there has been a lot of changes in the FE, I have often decompiled
it in the past without any problems, but might this be relevant?

I'd really appreciate some insight and am happy to provide more
information if necessary.

Regards
Marguerite

date: Wed, 2 Jul 2008 22:50:00 -0700 (PDT)   author:   unknown

RE: Users have dbSecFullAccess but can't read connect string   

Remember that with a split db, all users must have read/write/edit/delete 
rights to the be file AND the folder it resides in. Also, all computers need 
to be updated with the latest service paks. Even then, sometimes I have had 
to reload the computer totally because the registry has gotten fried. Very 
common in Windows.

"mjt7email-ggroups@yahoo.co.uk" wrote:

> Hello Everyone
> 
> Using Access 97 and a split db. The problem is sorted, but I wonder if
> anyone can tell me why it may have happened so I can avoid it in the
> future.
> 
> Users with dbSecFullAccess on the tables container can't read the
> connect string if the tables have been previously linked by another
> user. The connect string for the second user is "<unknown>" without
> the quotes.
> 
> What happened to dbSecFullAccess on the tables container, or more
> precisely, what did I do to corrupt it?
> 
> Info:
> 
> BE mdb on server, FE mde on local PC's. Both databases are secured
> using a devel.mdw and the company uses a site.mdw.
> 
> If I'm creating a lot of new queries or changing the BE tables, I
> delete the linked tables and toggle permission for the tables
> container between dbSecFullAccess and dbSecNoAccess. The tables are
> linked and group permission for the new queries is applied.  Would
> this toggling for linked tables invite the problem?
> 
> If there has been a lot of changes in the FE, I have often decompiled
> it in the past without any problems, but might this be relevant?
> 
> I'd really appreciate some insight and am happy to provide more
> information if necessary.
> 
> Regards
> Marguerite
>

date: Tue, 15 Jul 2008 06:27:01 -0700   author:   Golfinray