Cell Save & Restore

Hi, I want to know more about “Cell Save & Restore”. I have read the manual, it is confusing on the subject. Is there perhaps a video or further resources available on the subject?
My purpose is this:
The original workbooks I send out to my clients never get data entered. They are immediately saved as an .xlsc to which the client will make their personalized changes. They will then save this as a master file. The one that is then opened each time to create a job, it then gets saved as another .xlsc with the job reference in the file name. So eventually there is a whole bunch of .xlsc job files and only one .xlsc master file which typically remains the same. So when I push out an update, (only minor changes), to the original workbook, it would be good if the client could either, still open the masterfile with the updated workbook, or be able to save their customizations to be added to the new master file that they will need to create.

There are video tutorials here:


In your case, it would be better to configure your main Excel workbook to save user data into normal workbooks.
Or the Cell Save & Restore format may be useful but without more info about how your end users enter data into your workbooks, it will be difficult to give you proper advice.
There is also a FAQ topic about VBA code that could be helpful to you:
I updated my original workbook. What about existing saves made by end users?

I have found through testing that the user can still open previous files with the updated workbook and they don’t reflect the updates. But the new save do.
This serves my purposes.

For me; I have found the best way around this issue (since mine is setup the same way as yours; I distribute a main .exe and the user files are allways .xlsc files).
Just create (compile) the xlsc files using your older XLS compiler, that way it can still be opened on any previous user’s computers, then I create/compile the actual .exe using the newest XLS Padlock in order to get needed fixes (for WIN updates, etc).
Only the .exe needs to be the newest from XLS (to apply any fixes, etc) and the xlsc file does NOT need to be compiled with the latest XLS Padlock (If you do mistakenly compile your xlsc master uing the latest XLS Padlock, then your user(s) will no longer be able to open the xlsc file unless they have the latest exe as well).
For me this requires 2 computers; 1 with the older XLS Padlock for compiling the master work file (xlsc), and the other computer just compiles the .exe (using the newest version of XLS Padlock).

Then you will just compile these both (the exe and your xlsc file) into an installer to distribute your program.

Hope this helps, as this has worked for me for years now, as I got tired of fielding calls regarding not being able to open an xlsc file.