Thanks very much for going to these lengths to assist, I appreciate it.
I’ve now had a chance to examine scanlibrary and suppose that registercustomstatement registers individual statements from the statements database rather than all of them, and would still require the statements database to be open.
I’d prefer not to have additional databases in our factory computers to get lost or messed with or forgotten about, and in fact in the past I have folded several support databases (like customer and product files) into permanent variables in the one Panorama 6 file left on each of our factory computers to avoid having to worry about them. So in this case I decided to put my custom statements into one procedure in that P6 file separated by case statements, so I can call them as needed. I’ve just completed this and it works well.
Although it also worked putting the procedures into a dictionary and using execute to run them, I went for one procedure because it’s easier to follow.
When the time comes, I’ll probably use the scanlibrary solution when I switch my numerous head office files to Panorama X unless by then you’ve come up with a final custom statements solution as in P6.
David Duncan