How to link a table from database protected by mdw file

Access security has no "shortcuts".

However, you can use owner permission queries. You only
need permission to create the links, not to use them.

(david)


"Rick Brandt" wrote in message
et...
Alek Luchnikov wrote:
Hello, Albert!
You wrote on Tue, 13 Feb 2007 08:48:15 -0700:

I just want prevent users modify data in database. I think that a
protected by mdw database more securely than protected by password.
I find an example how to link tables from db protected by password
and I think there are an example how to link tables from db protected
by mdw but I can't find them. If anybody have one give mÕ please link
or send by email.

You cannot create or use a link to a table in a secure MDB unless the file
you
are creating the link in was opened using the same workgroup that was used
to
secure the secured file. You can open a new workspace in code that uses
the
secure workgroup and get at data programmatically, but you cannot create a
persistent link.

Access security has no "shortcuts".

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

david@epsomdotcomdotau wrote:
Access security has no "shortcuts".

However, you can use owner permission queries. You only
need permission to create the links, not to use them.

(david)

That would still require that you use the appropriate workgroup unless the
person who set up security gave those permissions to "Admin" or "Users".

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

That would still require that you use the appropriate workgroup unless the
person who set up security gave those permissions to "Admin" or "Users".

????

The users would use the default workgroup, with no extra permissions
given to anything.

The Owner Permission Queries would use owner permissions. You don't
need to use 'an appropriate workgroup' to use an Owner Permission Query.

you only need permission to create the links, not to use them.

"Rick Brandt" wrote in message
t...
david@epsomdotcomdotau wrote:
Access security has no "shortcuts".

However, you can use owner permission queries. You only
need permission to create the links, not to use them.

(david)

That would still require that you use the appropriate workgroup unless the
person who set up security gave those permissions to "Admin" or "Users".

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

david@epsomdotcomdotau wrote:
That would still require that you use the appropriate workgroup
unless the person who set up security gave those permissions to
"Admin" or "Users".

????

The users would use the default workgroup, with no extra permissions
given to anything.

The Owner Permission Queries would use owner permissions. You don't
need to use 'an appropriate workgroup' to use an Owner Permission
Query.

Have you tried this? If I use the wrong workgroup then the "owner" of the query
will be "Unknown" during the session. It seems to me that that would be asking
Access "let me run this query with the owner's permissions, without having any
idea who that owner is".

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

David, Rick

You're now talking about different things. The OP wanted to open an
unsecure mdb and link to a secure mdb.

So David, there won't be any RWOP queries in the unsecure mdb, so yes you
would need an appropriate workgroup to link to the secure mdb. But if you
are no longer talking about the OP's scenario, then you are right.

Rick, an owner of 'unknown' works just fine for RWOP queries. I do this all
the time (production mdw is different than development mdw and production
doesn't contain the 'owner')

--
Joan Wild
Microsoft Access MVP
"Rick Brandt" wrote in message
t...
david@epsomdotcomdotau wrote:
That would still require that you use the appropriate workgroup
unless the person who set up security gave those permissions to
"Admin" or "Users".

????

The users would use the default workgroup, with no extra permissions
given to anything.

The Owner Permission Queries would use owner permissions. You don't
need to use 'an appropriate workgroup' to use an Owner Permission
Query.

Have you tried this? If I use the wrong workgroup then the "owner" of the
query will be "Unknown" during the session. It seems to me that that
would be asking Access "let me run this query with the owner's
permissions, without having any idea who that owner is".

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

Yes, the RWOP queries were MY suggestion. The OP did not
suggest RWOP queries as a possible solution to his problem.

I wasn't doing it explicitly to correct the information that had been
posted.

(david)




"Joan Wild" wrote in message
...
David, Rick

You're now talking about different things. The OP wanted to open an
unsecure mdb and link to a secure mdb.

So David, there won't be any RWOP queries in the unsecure mdb, so yes you
would need an appropriate workgroup to link to the secure mdb. But if you
are no longer talking about the OP's scenario, then you are right.

Rick, an owner of 'unknown' works just fine for RWOP queries. I do this
all
the time (production mdw is different than development mdw and production
doesn't contain the 'owner')

--
Joan Wild
Microsoft Access MVP
"Rick Brandt" wrote in message
t...
david@epsomdotcomdotau wrote:
That would still require that you use the appropriate workgroup
unless the person who set up security gave those permissions to
"Admin" or "Users".

????

The users would use the default workgroup, with no extra permissions
given to anything.

The Owner Permission Queries would use owner permissions. You don't
need to use 'an appropriate workgroup' to use an Owner Permission
Query.

Have you tried this? If I use the wrong workgroup then the "owner" of
the
query will be "Unknown" during the session. It seems to me that that
would be asking Access "let me run this query with the owner's
permissions, without having any idea who that owner is".

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com