![]() |
Locking VBA code via Project properties but cannot save the workbook over itself
Hi All, is there a way you can lock your VBA code via the VBA project
properties but also have the user save the workbook without being promted to unlock the VBA project?? I have locked my code but connot save the workbook without unlocking my VBA code. Thanks SK |
Locking VBA code via Project properties but cannot save the workbook over itself
Hi
It is just a simple macro .. Im saving as file type - Excel 97 - Excel 2003 & 5.0 / 95 format. When the file reaches the stage where its saving in 5/95 format it displays a message that it cannot save the workbook with the VBA project being protected. Very weird indeed. I am running Excel 2003. This is consistent behaviour with all my files and other users are reporting the same issue. "Dave Peterson" wrote in message ... This isn't usual behavior. You should be able to save your workbook with the project protected with no prompts. Any chance you have a misbehaving macro that causes an error message to appear? Shane wrote: Hi All, is there a way you can lock your VBA code via the VBA project properties but also have the user save the workbook without being promted to unlock the VBA project?? I have locked my code but connot save the workbook without unlocking my VBA code. Thanks SK -- Dave Peterson |
Locking VBA code via Project properties but cannot save the workbook over itself
From memory you can't save back down to 95.
As there was a lot of new coding stuff added in 97 that isn't compaitable with 95. This would be your problem. Try "save as" a Offcice 95 version and see the message "Shane" wrote in message ... Hi It is just a simple macro .. Im saving as file type - Excel 97 - Excel 2003 & 5.0 / 95 format. When the file reaches the stage where its saving in 5/95 format it displays a message that it cannot save the workbook with the VBA project being protected. Very weird indeed. I am running Excel 2003. This is consistent behaviour with all my files and other users are reporting the same issue. |
Locking VBA code via Project properties but cannot save theworkbook over itself
Ahhh. 5.0/95 didn't have protected projects. And excel is smart enough to stop
users from simply saving in xl95 to see your top secret code. Do you really need xl95 format? That's pretty darn old. I'm kind of surprised that nothing else broke! Shane wrote: Hi It is just a simple macro .. Im saving as file type - Excel 97 - Excel 2003 & 5.0 / 95 format. When the file reaches the stage where its saving in 5/95 format it displays a message that it cannot save the workbook with the VBA project being protected. Very weird indeed. I am running Excel 2003. This is consistent behaviour with all my files and other users are reporting the same issue. "Dave Peterson" wrote in message ... This isn't usual behavior. You should be able to save your workbook with the project protected with no prompts. Any chance you have a misbehaving macro that causes an error message to appear? Shane wrote: Hi All, is there a way you can lock your VBA code via the VBA project properties but also have the user save the workbook without being promted to unlock the VBA project?? I have locked my code but connot save the workbook without unlocking my VBA code. Thanks SK -- Dave Peterson -- Dave Peterson |
All times are GMT +1. The time now is 10:18 AM. |
Powered by vBulletin® Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
ExcelBanter.com