|
I've most commonly seen this error generated by LotusScript code that tries to instantiate an invalid database object handle and then tries to work with it. This could be happening if the server and/or file path are incorrect or if the current machine cannot connect to the target server, but it is more likely that the user does not have access to open the target database.
Do you have comments on this Ask the Expert Q&A? Let us know.
Related information from SearchDomino.com:
Tip: Troubleshoot Lotus Notes Out of Office (OOO) agent error messages
Tip: Workaround for @DBLookup error
|
