I’m attempting to call the new version 6 “Close” method on the NotesUIDatabase object after performing performing some automated printing tasks on numerous databases for a client.
Whenever the Close method is called I get a message “Connot close the context database.”
I’ve searched all of the LDD here and tried the various applicable suggestions and all fail in one way or another.
The sendmessage examples do actually close the notes application but leave it in a corrupted state that forces rebooting the system in order to allow it to work again.
The various ZapNotes programs available sometimes work to avoid that, but they don’t lend themselves from being called without any user interaction with the programs being required.
I don’t actually want to exit the notes applicaiton I “simply” want to close the current (UI) database so I can open the next database to be printed with and repeat the entire process until all applicable databases have been printed.
I originaly tried doing this from the C API but the EditorPrintNoteToBitmap function has so many flakey / unpredictable behaviors that it is practically worthless.
Performing the message printing tasks from VB via the noes OLE automation interfaces works reasonably well other than the occasional unexpected popup messages and not being able to close the database so I can move to the next database.
Any suggestions on how to resolve closing the database via automation from VB?
Is it possible to call the "@Command(FileCloseWindow]) or equivalent to close the database instead of exiting notes from VB?
I’ve upgraded to the Notes version 6.0.1.CF3, and have the latest of the various API’s installed.