R
rdemyan via AccessMonster.com
My application is workgroup secured and I'm using RWOP queries on back-end
tables where all permissions have been revoked. I have a routine that runs at
startup to link all tables. It basically follows the following topic in
Access Securitiy FAQ
14.3 No Permissions necessary - Using the .Connect property to relink tables
So for well over a year now the routine has run flawlessly. I recently added
a new table to the backend and I can not link it. It never shows up as
linked in the dbWindow. I can link it if I use the Access menu bar and do it
manually, but this is not what I want.
I've checked the table in the backend and it has the exact same permissions
(or more accurately, lack thereof) as the other tables in the backend. The
owner is the same as the other tables, everything is the same. After linking
the table using the MS Access menu bar item, I checked the front-end
permissions and they are the same on that table as any other linked table
(namely, full permissions in the frontend, no permissions in the backend).
It is difficult to determine the error since the Microsoft code requires that
On Error Resume Next be used. However, it appears to be error 3265:
Application-defined or object-defined error.
I think I'm gonna need help from one of the responders who is well-versed in
workgroup security issues. Somebody like TC maybe?
Thanks.
tables where all permissions have been revoked. I have a routine that runs at
startup to link all tables. It basically follows the following topic in
Access Securitiy FAQ
14.3 No Permissions necessary - Using the .Connect property to relink tables
So for well over a year now the routine has run flawlessly. I recently added
a new table to the backend and I can not link it. It never shows up as
linked in the dbWindow. I can link it if I use the Access menu bar and do it
manually, but this is not what I want.
I've checked the table in the backend and it has the exact same permissions
(or more accurately, lack thereof) as the other tables in the backend. The
owner is the same as the other tables, everything is the same. After linking
the table using the MS Access menu bar item, I checked the front-end
permissions and they are the same on that table as any other linked table
(namely, full permissions in the frontend, no permissions in the backend).
It is difficult to determine the error since the Microsoft code requires that
On Error Resume Next be used. However, it appears to be error 3265:
Application-defined or object-defined error.
I think I'm gonna need help from one of the responders who is well-versed in
workgroup security issues. Somebody like TC maybe?
Thanks.