On Error Resume Next for backend with revoked table permissions

  • Thread starter Thread starter rdemyan via AccessMonster.com
  • Start date Start date
R

rdemyan via AccessMonster.com

I posted a different problem in General 1 regarding inability to link to
backends on another computer using my new copy of Access 2003.

I use RWOP queries with all permissions revoked on the back-end tables. As a
result, I have followed Microsoft's Access Security FAQ guide and am using On
Error Resume Next when I try to link.

However, the problem with linking to these "peer computer" backend files from
A2003, made me realize that I wasn't picking up the error. Instead, because
of On Error Resume Next, the code went along happily and reported that
linking occurred just fine, which it did not.

Maybe instead of On Error Resume Next, I should try to trap specific Err.
Numbers associated with linking to backend files where all table permissions
have been revoked. That way other errors (like the exclusivity error
encountered with A2003) will be shown to the user.

So, does anyone have a good list of the potential "permissions errors" that
should be allowed with Resume Next when linking to backends where all table
permissions have been revoked.

Thanks.
 
In my discussion of Access security, I make a brief mention of the
difference between the RefreshLink and TransferDatabase methods. You
might want to check out the TransferDatabase method. It's been a long
time since I wrote that piece, so the details are hazy.

Its on P 14 of
http://www.geocities.com/jacksonmacd/AJMAccessSecurity.pdf

As for trapping errors, I always find that Select Case works best. Put
in a CaseElse section, and make it a breakpoint. That gives you the
opportunity to find out what errors are raised at different times.



I posted a different problem in General 1 regarding inability to link to
backends on another computer using my new copy of Access 2003.

I use RWOP queries with all permissions revoked on the back-end tables. As a
result, I have followed Microsoft's Access Security FAQ guide and am using On
Error Resume Next when I try to link.

However, the problem with linking to these "peer computer" backend files from
A2003, made me realize that I wasn't picking up the error. Instead, because
of On Error Resume Next, the code went along happily and reported that
linking occurred just fine, which it did not.

Maybe instead of On Error Resume Next, I should try to trap specific Err.
Numbers associated with linking to backend files where all table permissions
have been revoked. That way other errors (like the exclusivity error
encountered with A2003) will be shown to the user.

So, does anyone have a good list of the potential "permissions errors" that
should be allowed with Resume Next when linking to backends where all table
permissions have been revoked.

Thanks.
Click to expand...

**********************
(e-mail address removed)
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security
 
Back
Top