 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Create a macro in Excel 2007 to disable save</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/diable-save/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/diable-save/</link>
	<description></description>
	<lastBuildDate>Sat, 25 May 2013 16:32:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: donethat</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/diable-save/#comment-89277</link>
		<dc:creator>donethat</dc:creator>
		<pubDate>Fri, 11 Mar 2011 12:13:08 +0000</pubDate>
		<guid isPermaLink="false">#comment-89277</guid>
		<description><![CDATA[I do this regularly. I have a number of Excel workbooks on the server with literally 100+ &quot;reports&quot; driven by SQL. IE: my own query system.

I do NOT want my users to save these workbooks. Why?
1. They are VERY large (huge VBA code structure).
2. If they save them, they could reexecute code which has been changed/fixed/improved in the current version.
3. It would allow my code in the hands of unauthorized users.

My users are trained to copy the worksheet (already flat data, no formulas other than occasional formatting) to a new workbook and save THAT to their area.
This technique has worked great for 10 years!

You must:
1) Make the workbook read-only in your &quot;production directory&quot; (as suggested by Chippy088) AND
2) Disable the Save/Saveas function in VBA AND
3) Detect the directory you are running in and only allow resaving the program on exit IF you are in your &quot;development directory&quot;. 

To &quot;publish&quot; new code, copy the dev xls to the production directory and make it read-only.

No one has found a way to get around this so far.

Gary

PS: I would have provided some code but I did this so long ago it will take me sometime to dig it out. However, if you need - respond and I will do so.]]></description>
		<content:encoded><![CDATA[<p>I do this regularly. I have a number of Excel workbooks on the server with literally 100+ &#8220;reports&#8221; driven by SQL. IE: my own query system.</p>
<p>I do NOT want my users to save these workbooks. Why?<br />
1. They are VERY large (huge VBA code structure).<br />
2. If they save them, they could reexecute code which has been changed/fixed/improved in the current version.<br />
3. It would allow my code in the hands of unauthorized users.</p>
<p>My users are trained to copy the worksheet (already flat data, no formulas other than occasional formatting) to a new workbook and save THAT to their area.<br />
This technique has worked great for 10 years!</p>
<p>You must:<br />
1) Make the workbook read-only in your &#8220;production directory&#8221; (as suggested by Chippy088) AND<br />
2) Disable the Save/Saveas function in VBA AND<br />
3) Detect the directory you are running in and only allow resaving the program on exit IF you are in your &#8220;development directory&#8221;. </p>
<p>To &#8220;publish&#8221; new code, copy the dev xls to the production directory and make it read-only.</p>
<p>No one has found a way to get around this so far.</p>
<p>Gary</p>
<p>PS: I would have provided some code but I did this so long ago it will take me sometime to dig it out. However, if you need &#8211; respond and I will do so.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chippy088</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/diable-save/#comment-89275</link>
		<dc:creator>chippy088</dc:creator>
		<pubDate>Fri, 11 Mar 2011 11:11:25 +0000</pubDate>
		<guid isPermaLink="false">#comment-89275</guid>
		<description><![CDATA[I am guessing you want users to have access to the workbook, but you don&#039;t want to allow it to be over written.

Have you thought about holding the workbook on a server and make it, and the folder it is in, read only. 

You can also password protect portions of it, to stop overwriting. This method does not stop users saving it locally and then working on it. It will only stop the master copy being changed before other users want to access it.

Save is an internal function of excel, so I think it might be a complex and, possibly, unwanted way of disabling save. I have never seen, or heard, of it being done, if it could be, then i think Microsoft would have reference to it, in their knowledge base. It would involve trapping the save function call, and redirecting it, in assembler. Not a task for novices, and it might mess up functionality of excel.]]></description>
		<content:encoded><![CDATA[<p>I am guessing you want users to have access to the workbook, but you don&#8217;t want to allow it to be over written.</p>
<p>Have you thought about holding the workbook on a server and make it, and the folder it is in, read only. </p>
<p>You can also password protect portions of it, to stop overwriting. This method does not stop users saving it locally and then working on it. It will only stop the master copy being changed before other users want to access it.</p>
<p>Save is an internal function of excel, so I think it might be a complex and, possibly, unwanted way of disabling save. I have never seen, or heard, of it being done, if it could be, then i think Microsoft would have reference to it, in their knowledge base. It would involve trapping the save function call, and redirecting it, in assembler. Not a task for novices, and it might mess up functionality of excel.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: technochic</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/diable-save/#comment-89180</link>
		<dc:creator>technochic</dc:creator>
		<pubDate>Wed, 09 Mar 2011 21:58:06 +0000</pubDate>
		<guid isPermaLink="false">#comment-89180</guid>
		<description><![CDATA[Why do you need to disable save? What is it you are trying to acheive? Do you just want to protect an existing spreadsheet?]]></description>
		<content:encoded><![CDATA[<p>Why do you need to disable save? What is it you are trying to acheive? Do you just want to protect an existing spreadsheet?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/9 queries in 0.014 seconds using memcached
Object Caching 296/299 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-25 17:24:47 -->