On Error GoTo 0 causes weird error

[Alabaster2100]

I have an application that I'm modifying with a new search function. In order to trap for records not found I use a rst.move with on error move next. Once I've finished this trap I normally would set on error goto 0 in order to re-enable error trapping.
The application has had a very extensive security model setup and when I log in as one of the users and try my search I get an error of
Run-Time Error 3033
"You do not have permissions to use the MsysTables object"

This error does not occur if I comment out the on error goto 0.
Can anyone shed some light on this, my search is looking at a table of serial numbers, nothing special...

Thanks in advance

Peter

~~~~~~~~~~~~~~~~~~~~~
Peter
-Self educated Geek-
If it can be fixed...
I can break it!

 

[tbassngal]

Sounds to me like you are not technically the administrator of that database. That is a system object to which you have no permissions. The only way I've ever been able to get around errors such as these is is to create a new database by importing all objects, then creating a new security file. OR speak to the owner of the database and have them administer the correct permissions. Why do you need to use the MsysTables object? It's a system generated/hidden file?

 

[Alabaster2100]

Your right Administrator does not have "admin" privledges. and dbdev is the owner. Im not trying to manipulate the msystables, at the moment I cant even find it (I see all other Msys tables though) All I'm trying to do is restore error trapping with "on erro go to 0", but if I put that in I get the error RT3033.

Very Bizzaar

Peter

~~~~~~~~~~~~~~~~~~~~~
Peter
-Self educated Geek-
If it can be fixed...
I can break it!