Yes! Isaac. This is the option I used. I did not supply a password to open read-only, I supplied a password to modify.
I followed your sequence and you are correct it saves a copy; read-only can be by-passed by renaming, so it is not a very sound method to prevent modification
(
Thank you for responding.
Well, I see your point. If you want to prevent Copies, you may have to get more creative.
I used to do a LOT of creative stuff in Excel VBA to deploy "applications" that were essentially workbooks on steroids.
Some things you can try if you feel like it:
1) make the workbook un-useable if macros are not enabled. (first step to make anything else worth it). how? hide all sheets except a splash page, which says "you have macros disabled - you must enable - etc etc". the workbook_close event will hide all sheets EXCEPT this one, and you let it run every time you as a developer close the book.
2) workbook_open event: this will UNHIDE the true, useful sheets.....and HIDE the splash page 'you must enable macros' sheet. (which won't run if macros are disabled).
3) finally, add your desired effect - in the workbook_beforesave event, Cancel it and let the person know...no can do.
4) pw protect your vba project, as always.