Hmm … ok, that looks like some of the documentation I’ve read.
What I really need to accomplish is ensure that Panorama correctly “compiles” the procedures when the database is closed.
Here are the steps that sometimes, but not always, leads to an error:
- Open a shared database (seems to have to be shared)
- Open a procedure
- Note: the Panorama “status bar” says, “Procedure opened”
- Quit Panorama
- Launch Panorama and re-open the database
- Attempt to execute the procedure that had been opened from the “Action” menu
Sometime, this leads to a “this procedure cannot be used: it contains one or more incorrect steps” error dialog, but not always.
If, at this point, the procedure is opened, and the “Check Procedure” button is clicked (so that the “Panorama status” says, “Procedure OK.”), then the procedure works as it should and no error occurs, even after Panorama is quit and re-launched.
I would just like a way to ensure that all “open/uncompiled” procedures are compiled and saved so that they always work when the database is opened up.
Or, maybe it’s just me … and my network has “dirty bits” flying over it!
Thanks for your time, patience, and assistance!