When I use the “Quit Panorama X” menu function in Pan X, sometimes Pan X quits, and sometimes it doesn’t.
I thought it might be that some of my open databases were “Edited”, and could not be closed without first saving. However, sometimes Pan X will quit, with some of my open database being “Edited”.
Looks like Pan X 10.2.0 b26 fixed an issue allowing Pan X to close even if a current record is being modified. When my issue occurs, there are no records being modified.
In case it matters, the databases in question are shared.
Any suggestions?
Also, in general, what does Pan X do when it quits shared databases? Does it sync, save, and then close?
I just experienced this a few minutes ago and see it often. I have to find which file shows that it’s been edited then save. Once that’s done Quit works again. Ideally, I’d be asked if I want to save changes
Previously, this setting was turned off on my computer. Do you know would happen to a database that was closed (using the quit command), and not saved prior to closure? Would Pan X save the edited data in that database? Or would those edits likely be lost?
I’ve had this issue for some time with Panorama not quitting until I fished through windows to find the one marked Edited. Panorama just sat there otherwise.
I had no computers with the Ask option checked. Today I’m being asked about reviewing and saving. Thank you, Kurt.