There must be more to the story, because Panorama 6 will also normally close the file if you click on the close box. You must have done something special to your file to make this happen, I have a couple of ideas as to what you may have done.
Back in the Panorama II days, there was no “secret” window feature, so the Power Team databases would simulate this by opening a small form window off the edge of the screen, so it was invisible. Perhaps you are using a method like this – it would work the way you describe, and if you have been doing this for 25 years, that would take you back into the Panorama II era.
Another way this could be done starting with Panorama 4 would be by creating a
.CloseDatabase procedure and putting in a
closewindowkeepsecret statement if there is only one window open for this database. Panorama X does not support the
. CloseDatabase procedure, so this won’t work in Panorama X. But this is definitely not a standard feature of Panorama 6. If this is what you did, I congratulate you on reading the Panorama 6 documentation closely, as this is only mentioned in passing on page 398 of the Panorama 6 Formulas & Programming book.
The way Apple’s API’s handle documents do not allow for something like a
.CloseDatabase procedure, so this won’t be added to Panorama X. It is possible, however, than an database option could be created to prevent a database from ever closing – making it secret if you try to close it. This is already done for Panorama’s library databases. I’ve created a BitBucket entry for this idea. Of course if a database had this option set, you could not ever close it except for quitting Panorama, or turning off the option.
In the meantime, you could make a menu command that runs the
makesecret statement, but you would have to be careful to close the window with this menu command, and not the close box.
Also, there is nothing magical about the post statement – you could write your own code to switch to the secret window and perform any operation you want, for example to mark when you have been paid. You can look at the source code of the post statement for inspiration. In fact, I didn’t write the post statement – I think it was Dave Thompson. If I am misremembering that my apologies to the actual author. But the point is that it uses standard code that is available to anyone, the post statement simply makes this job a bit easier if you learn it.