For the last year, I have been in the process of reverting my Pan 6 files to Pan X. I have to say that in all of the years that I have seen Pan X, Jim has done a great job adding most of the features from Pan 6.
There is still one task that drives me crazy, and that is autosave.
In the 25-plus years that I have built my database in Pan 6, I have gotten into the habit of being able to build on one file, and after I finish, either resave the file with a new name or delete it so that it’s back to the way it was for the next task.
I have realized that in Pan X, the files automatically save, which has caused me a lot of pain since most of the time, I am just manipulating information but don’t want the file after manipulating it.
I have gotten into the habit whenever I call up a file to rename it something else, but sometimes this can screw me up.
In using Excel, I noticed that at the top of the datasheet, there is an AutoSave tab so that the file will not update until you want to update it
I find this system very handy and wonder if there is some hidden trick to stop the Autosave on Pan X? If not, is it possible for future editions of Pan X to have an autosave button like Excel has???
The “Autosave” button in Excel’s toolbar is NOT the same as the Autosave feature in macOS or in Panorama X. In Excel it means automatically saving the file into the cloud, i.e. into Microsoft’s OneDrive. It does not work with local files on your Mac.
Panorama X on the other hand utilizes the macOS features Autosave and Revert.
Sal, you have several options, if you just want to experiment with your databases and do not want to keep the changes:
Use the File > Duplicate menu command. Then you can edit the file and then decide to keep or to discard it.
Edit your original file, and use the File > Revert To > Browse All Versions menu command, if you do not want to keep your modifications.
Microsoft Excel is a cross platform program that runs on macOS and Windows. Most likely they have built their own bespoke system for document management, rather than using the built in document management APIs provided by Apple. This is what Panorama 6 did (actually we had no choice because those earlier versions of Panorama pre-dated Apple’s document management code).
For Panorama X the decision was made to eschew bespoke solutions and use Apple’s provided solutions whenever possible, with the goal of making Panorama work in a standard way like most other macOS applications. I think this decision has served Panorama well, but it has required some adjustments for users of earlier Panorama versions that had gotten used to our previous bespoke solutions. You can’t make an omelet without breaking some eggs, as they say.
Apple’s document management system does not provide for disabling Autosave, in fact, Autosave is an integral part of their system that I don’t think could be removed without substantial rearchitecting of their system. Obviously I am not expecting that to happen at this late date.
The closest you can get is to enable this setting in the General panel of the system Preferences/Settings window.
Note that this setting would apply to ALL applications that use Apples document management API, not just Panorama. As far as I know there is no way for Panorama to individually opt out of this setting.
Mr. Rea and KJM, appreciate the feedback.
Each week, I update all my files with that week’s stuff. I then search for answers and manipulate the file, deleting things inside it to get the answers I need. So, the main file is unusable after I mess around with it.
So, to ensure that doesn’t happen in all my shells, I have put in an Initialize command. When I opened the file, it asked if I wanted to make a copy, rename it, and save it to the desktop. At least this gives me a chance but I still get screwed up now and then.
We are all stuck in our ways, for me I have had to rethink things and teach this old fart some new tricks after 25 years.
In Ventura and later - this setting has been moved to the Desktop & Dock panel of the System Settings window - about half way down in the Windows & Apps section. (It took me 15 minutes to find it…)
If you’re not doing so already, that might be doable via a procedure. Which could also include making a date stamped duplicate copy of your main file.
If some of your weekly search for answers manipulation is repeated that also could be automated via a procedure, saving the results in whatever detail and format makes sense for you. With forethought you can design your code so each step of analysis generates its results then restores the files to ready for the next step. Combining all those results in one final report. Then you don’t have to write it all at once; just add more analysis modules to the framework whenever you are ready.
Takes awhile to setup, but can save significant time weekly once working while also reassuring you the analysis was done correctly.
