>I guess I don't understand then what RWOP really means.  I always assumed
>that is was the owner of the tables in the backend.  Are you saying it is the
>owner of the query in the front end???
>
>If I go to Security --> User and Group Permissions and click on the Change
>Owner tab and select Object Type = Query, I see the following:
>
>1) My RWOP queries on the main backend tables all say the Current Owner is
><Unknown>.  These queries work just fine with no problems.
>
>2) My RWOP queries on the temporary tables (from the temp table) show the
>Current Owner is also <Unknown>.
>
>I still don't know what to do.
>
>Thanks. 
>
>>It is not the owner of the /link/ which is important to an RWOP query.
>>It is the owner of the /query/. You need to ensure that the owner of
>[quoted text clipped - 5 lines]
>>HTH,
>>TC

>> I guess I don't understand then what RWOP really means.
>
>Makes it kinda' hard to use them properly!
>
>> I always assumed that it was the owner of the tables in the backend.
>
>Not sure I understand what you mean by that sentence. "An RWOP query is
>the owner of the tables in the backend"?
>
>Here is what you need to know. A normal (non RWOP) query is executed
>with the permissions of the user who is running the query. But an RWOP
>query is executed with the permissions of the user who /owns/ the
>query, regardless of which user is actually running it. So, an RWOP
>query can let the current user do things which he is normally not
>entitled to do.
>
>HTH,
>TC

>TC I appreciate your patience.  Please bear with me as using RWOP is the
>basis for my security and I realize now that I don't completely understand it.
>
>1) I thought that the word "Owner" in RWOP meant the owner of the backend
>tables not the front-end query.
>
>2) Then my  problem is that the owner of my RWOP query (located in the front
>end) on the temp tables is not a member of the workgroup used to secure the
>model temporary database.  If DBOWNER isn't a member he couldn't possibly
>have any permissions on those temporary tables.  Please confirm that this is
>correct.
>
>3) Now I'm wondering about my main backend tables.  I used the development
>workgroup file to secure both the front end and main backend. So, that
>explains why I have no problems with my RWOP queries on the main backend
>tables when using the development workgroup file.
>
>When using the distribution workgroup file, however, DBOWNER is, by design,
>not a member of that workgroup file.  This explains why when looking at the
>owner of the front-end queries when using the distribution workgroup file,
>that owner is displayed as <Unknown>.  But if only the distribution workgroup
>file is used, how does Access know who the owner of the RWOP is?
>
>I really want to make sure I understand this, so I would appreciate your
>confirming statements that I've made that are correct.
>
>Thanks.
>
>>> I guess I don't understand then what RWOP really means.
>>
>[quoted text clipped - 14 lines]
>>HTH,
>>TC

>Yes, let's continue this tomorrow.
>
>Even though the RWOP queries on the temp DB tables now function without error,
>I'm suddenly having problems with the workgroup files.
>
>I was doing some testing at trying to open the model temporary database with
>the development and distribution workgroup files.  I didn't think I would be
>able to open it, at least that's the way I designed it.  Temp DB opened no
>problem.  I thought I had secured it with the NoAccess workgroup file.  I can
>now open the Temp DB with these other workgroup files even with users that
>are not present in the NoAccess workgroup file (but are present in either the
>development or workgroup file).  I cannot open the Temp DB with just the
>regular system.mdw file (unaltered in any way by me).
>
>So, I don't know what's going on here with this.
>
>Thanks.
>
>>Got it. I am off now (have a client waiting) but will be back on
>>tomorrow.
>>
>>Cheers,
>>TC

>Didn't get your 2:05 post until well after my last post.  Let me state the
>current application strategy.
>
>1) Front end - Owner is DBOWNER. Secured by developer workgroup file.  Client
>gets distribution workgroup file.
>
>2) Main back end - Owner is DBOWNER.  Secured by developer workgroup file.
>Client gets distribution workgroup file. All permissions revoked on the
>tables. 
>
>3) Model temp DB - used in the creation of the instantiation of temporary
>database.  Owner is TEMPOWNER. Secured by NoAccess workgroup file.  All
>permissions revoked on the tables.
>
>DBOWNER is not a user in NoAccess workgroup file. Client does not get this
>workgroup file or any derivative of it.  This is what I meant when I said
>that the client doesn't have any workgroup file available to them to open
>this model temp DB or it's instance during any current session in which the
>front end is running (poor wording on my part in the post).   I don't want
>the client to be able to open either the model temporary database or it's
>instance.
>
>Thanks.
>
>>TC I appreciate your patience.  Please bear with me as using RWOP is the
>>basis for my security and I realize now that I don't completely understand it.
>[quoted text clipped - 29 lines]
>>>HTH,
>>>TC

>It's still a bit hard to comment on your setup, because of the way you
>phrase your descriptions. For example, you say that "no workgroup file
>is distributed for the model temporary database". That /sounds/ like it
>makes sense - bit it doesn't. When you start Access, eg. by
>double-clicking a database file, it /always/ selects a workgroup file
>to use for that run of Access. If code within that database, writes to
>or reads from another database, that other database will be accessed
>using the workgroup file that Access selected for that run. So there is
>no way that you can access the other database "without a workgroup
>file" - regardless of which workgroup files you did or didn't
>distribute to the user.
>
>But I guess the proof is in the pudding. Try to break your own security
>by accessing the confidential data in either database without a valid
>username/password. If /you/ can't do that, the odds are that the user
>can't either :-)
>
>Good luck!,
>TC

>Ok, I hear what you say. Let me restate this in my own terms to be sure
>I understand it.
>
>- You have a main database db#1.
>
>- You have a copy (db#2) of the model temporary database.
>
>- You start db#1, probably with a shortcut that uses the /wrkgrp switch
>to select the proper workgroup file, wg#1.
>
>- The user logs on with a username/password, say, Fred/whatever.
>
>- User Fred of workgroup file wg#1 has sufficient permissions to read &
>write data from & to db#2, but he does /not/ have sufficient permision
>to open db#2 directly (by double-clicking it)?
>
>Yes? No?
>
>TC

>It's still a bit hard to comment on your setup, because of the way you
>phrase your descriptions. For example, you say that "no workgroup file
>is distributed for the model temporary database". That /sounds/ like it
>makes sense - bit it doesn't. When you start Access, eg. by
>double-clicking a database file, it /always/ selects a workgroup file
>to use for that run of Access. If code within that database, writes to
>or reads from another database, that other database will be accessed
>using the workgroup file that Access selected for that run. So there is
>no way that you can access the other database "without a workgroup
>file" - regardless of which workgroup files you did or didn't
>distribute to the user.
>
>But I guess the proof is in the pudding. Try to break your own security
>by accessing the confidential data in either database without a valid
>username/password. If /you/ can't do that, the odds are that the user
>can't either :-)
>
>Good luck!,
>TC

>Okay, I think I have most of it figured out, but I'm still having problems.
>Right now my db#2 can be opened with Workgroup file #1 and I didn't think
>that should be the case.  Here are the particulars
>
>1) DB#1 secured by Workgroup file #1.  Owner of all items is DBOWNER
>2) DB#2 secured by Workgroup file #2.  Owner of all items is DBOWNER
>3) Workgroup file #2 users are only Admin and DBOWNER.
>4) The front end, DB#1, uses RWOP queries on the tables in the backend, DB#2.
>Linking is done as outlined in Access Security FAQ, Item 14.3, No permissions
>necessary.
>It says in Item 14.3 that a user needs to have Open/Run permissions on DB#2.
>DBOWNER in DB#2 has full permissions on the tables.
>
>I have a custom group called PowerUsers that is in both Workgroup files.  Every user in both workgroup files (except the Admin user) is also a member of the PowerUsers group.
>When Open/Run for the database (DB#2) is set for PowerUsers, everything works
>fine.  DB#2 is linked and RWOP queries can be accessed by all users.  However,
>any user in Workgroup file #1 can log on with Workgroup file #1 and open DB#2?
>??!  Note, except for DBOWNER, none of the other users in Workgroup file #1
>is listed in Workgroup file #2.
>
>If Open/Run for the DB#2 database is revoked for PowerUsers, then the RWOP
>queries cannot be accessed except by DBOWNER (which is not surprising, since
>DBOWNER is the owner for both dbs).  However, only Workgroup file #2 can be used to open db#2, which is what I want.
>
>So I don't know how to fix this. 
>
>Thanks for any help.
>
>>I forgot to comment on the linking.
>>
>[quoted text clipped - 7 lines]
>>>Good luck!,
>>>TC

>Okay, I think I have most of it figured out, but I'm still having problems.
>Right now my db#2 can be opened with Workgroup file #1 and I didn't think
>that should be the case.  Here are the particulars
>
>1) DB#1 secured by Workgroup file #1.  Owner of all items is DBOWNER
>2) DB#2 secured by Workgroup file #2.  Owner of all items is DBOWNER
>3) Workgroup file #2 users are only Admin and DBOWNER.
>4) The front end, DB#1, uses RWOP queries on the tables in the backend, DB#2.
>Linking is done as outlined in Access Security FAQ, Item 14.3, No permissions
>necessary.
>It says in Item 14.3 that a user needs to have Open/Run permissions on DB#2.
>DBOWNER in DB#2 has full permissions on the tables.
>
>I have a custom group called PowerUsers that is in both Workgroup files.
>When Open/Run for the database (DB#2) is set for PowerUsers, everything works
>fine.  DB#2 is linked and RWOP queries can be accessed by all users.  However,
>any user in Workgroup file #1 can log on with Workgroup file #1 and open DB#2?
>??!  Note, except for DBOWNER, none of the other users in Workgroup file #1
>is listed in Workgroup file #2.
>
>If Open/Run for the DB#2 database is revoked for PowerUsers, then the RWOP
>queries cannot be accessed except by DBOWNER (which is not surprising, since
>DBOWNER is the owner for both dbs).
>
>So I don't know how to fix this. 
>
>Thanks for any help.
>
>>I forgot to comment on the linking.
>>
>[quoted text clipped - 7 lines]
>>>Good luck!,
>>>TC

>> This fourm can be difficult.  Do you know how to edit a post that has already
>> been made.
>
>You can't. Sometimes (but far from always) you can cancel them, but you
>can not edit them.
>
>> Anyway I wanted to add the following two points.
>>
>[quoted text clipped - 5 lines]
>> DBOWNER is the owner for both dbs).  However, DB#2 now can only be opened by
>> Workgroup File #2, which is what I want.
>
>Robert, I'm quite happy to keep helping, but it's too hard to go back
>over previous posts & put them all together. See if you can make one
>more post, completely self-contained, which clearly summarizes what you
>have at present, and what doesn't work the way that it should.
>
>Cheers,
>TC