Quote:
quote:Originally posted by echovue
In my experience the less "monkeying around" access given to end users, the better.
|
Agreed. Someway...somehow...when a user enters an database with free reign, something always gets hosed. I'll never say anything bad about the staff I work with, but their capacity to destroy is beyond my understanding.
That said, after a user accessed one of our databases, I began getting the same error that the OP is getting. Interestingly enough, there is no switchboard involved. Just a sub in a module that prints a report and closes the database. That's it.
Compiling does not reveal anything wrong, and I find nothing wrong with the code itself. The error occurs after the report prints and the database is getting ready to close.
Incidentally, if anyone knows what the error number is for this error, I want to try some special error handling for it as a temporary fix until I can take the time to rebuild the whole database (and pray it works).
--------------------------------
Ben
"It's my way, or the Hemingway."
--------------------------------