<?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: Read the Manual</title>
	<atom:link href="http://www.dailydoseofexcel.com/archives/2006/03/29/read-the-manual/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dailydoseofexcel.com/archives/2006/03/29/read-the-manual/</link>
	<description>Daily posts of Excel tips…and other stuff</description>
	<lastBuildDate>Wed, 08 Feb 2012 23:58:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Dick Kusleika</title>
		<link>http://www.dailydoseofexcel.com/archives/2006/03/29/read-the-manual/#comment-32489</link>
		<dc:creator>Dick Kusleika</dc:creator>
		<pubDate>Wed, 21 May 2008 17:53:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1383#comment-32489</guid>
		<description>&lt;p&gt;Tigerp:  If you&#039;re using xl97 and an ActiveX control, change the TakeFocusOnClick property to False.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Tigerp:  If you&#8217;re using xl97 and an ActiveX control, change the TakeFocusOnClick property to False.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tigerp</title>
		<link>http://www.dailydoseofexcel.com/archives/2006/03/29/read-the-manual/#comment-32461</link>
		<dc:creator>Tigerp</dc:creator>
		<pubDate>Tue, 20 May 2008 14:41:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1383#comment-32461</guid>
		<description>&lt;p&gt;I am trying to write a simple macro to turn off auto-calculation on hitting the macro button. I recorded hitting Tools/Options/ Calculation and hitting the Manual calc radio button, but the resultant causes a runtime error [1004].&lt;br&gt;
Any ideas? Macro code:&lt;br&gt;
    With Application&lt;br&gt;
        .Calculation = xlManual &#039;(THIS IS THE LINE THAT FAILED)&lt;br&gt;
        .MaxChange = 0.001&lt;br&gt;
    End With&lt;br&gt;
    ActiveWorkbook.PrecisionAsDisplayed = False&lt;br&gt;
Thanks&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I am trying to write a simple macro to turn off auto-calculation on hitting the macro button. I recorded hitting Tools/Options/ Calculation and hitting the Manual calc radio button, but the resultant causes a runtime error [1004].<br />
Any ideas? Macro code:<br />
    With Application<br />
        .Calculation = xlManual &#8216;(THIS IS THE LINE THAT FAILED)<br />
        .MaxChange = 0.001<br />
    End With<br />
    ActiveWorkbook.PrecisionAsDisplayed = False<br />
Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randy Harmelink</title>
		<link>http://www.dailydoseofexcel.com/archives/2006/03/29/read-the-manual/#comment-24582</link>
		<dc:creator>Randy Harmelink</dc:creator>
		<pubDate>Tue, 05 Jun 2007 23:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1383#comment-24582</guid>
		<description>&lt;p&gt;&gt;&gt; Dim dtoh1, dtoh2, dtoh3, dtoh4, dtoh5, dtoh6, dtoh7, dtoh8, dtoh9, dtoh10 As Date&lt;/p&gt;
&lt;p&gt;I was under the impression that doesn&#039;t work as one would expect.  Each comma separates a full definition, so if you want them all to be type Date, you&#039;d need to code it as:&lt;/p&gt;
&lt;p&gt;Dim dtoh1 As Date, dtoh2 As Date, dtoh3 As Date, dtoh4 As Date, dtoh5 As Date,&lt;br&gt;
Dim dtoh6 As Date, dtoh7 As Date, dtoh8 As Date, dtoh9 As Date, dtoh10 As Date&lt;/p&gt;
&lt;p&gt;The original coding would define dtoh1 thru dtoh9 as type Variant&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>&gt;&gt; Dim dtoh1, dtoh2, dtoh3, dtoh4, dtoh5, dtoh6, dtoh7, dtoh8, dtoh9, dtoh10 As Date</p>
<p>I was under the impression that doesn&#8217;t work as one would expect.  Each comma separates a full definition, so if you want them all to be type Date, you&#8217;d need to code it as:</p>
<p>Dim dtoh1 As Date, dtoh2 As Date, dtoh3 As Date, dtoh4 As Date, dtoh5 As Date,<br />
Dim dtoh6 As Date, dtoh7 As Date, dtoh8 As Date, dtoh9 As Date, dtoh10 As Date</p>
<p>The original coding would define dtoh1 thru dtoh9 as type Variant</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wim Gielis</title>
		<link>http://www.dailydoseofexcel.com/archives/2006/03/29/read-the-manual/#comment-24548</link>
		<dc:creator>Wim Gielis</dc:creator>
		<pubDate>Mon, 04 Jun 2007 18:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1383#comment-24548</guid>
		<description>&lt;p&gt;Hi all, first comment here for me. Wonderful blog Dick and friends!&lt;/p&gt;
&lt;p&gt;Harald, here&#039;s an advanced one and perhaps not that useful, but still. What about checking whether variables have a good variable type. For instance, I just saw on a forum:&lt;br&gt;
Dim dtoh1, dtoh2, dtoh3, dtoh4, dtoh5, dtoh6, dtoh7, dtoh8, dtoh9, dtoh10 As Date&lt;br&gt;
Dim dt1, dt2, dt3, dt4, dt5, dt6, dt7, dt8, dt9, dt10 As Date &lt;/p&gt;
&lt;p&gt;Don&#039;t know if this is desirable / feasible.&lt;/p&gt;
&lt;p&gt;Cheers&lt;/p&gt;
&lt;p&gt;Wim Gielis&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hi all, first comment here for me. Wonderful blog Dick and friends!</p>
<p>Harald, here&#8217;s an advanced one and perhaps not that useful, but still. What about checking whether variables have a good variable type. For instance, I just saw on a forum:<br />
Dim dtoh1, dtoh2, dtoh3, dtoh4, dtoh5, dtoh6, dtoh7, dtoh8, dtoh9, dtoh10 As Date<br />
Dim dt1, dt2, dt3, dt4, dt5, dt6, dt7, dt8, dt9, dt10 As Date </p>
<p>Don&#8217;t know if this is desirable / feasible.</p>
<p>Cheers</p>
<p>Wim Gielis</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wendy</title>
		<link>http://www.dailydoseofexcel.com/archives/2006/03/29/read-the-manual/#comment-24406</link>
		<dc:creator>Wendy</dc:creator>
		<pubDate>Tue, 29 May 2007 18:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1383#comment-24406</guid>
		<description>&lt;p&gt;When user entered a date:  5/29/07  it was automatically changed into a formula.  The resulting number, 0.024630542,&lt;br&gt;
when date formatted, ended up with a date format of Jan00.  The problem was that the Transition Formula Entry option was set in the Tools, Options, Transition tab.  Unchecking this option fixed the problem.  The setting was designed to transition Lotus users into Excel, however in this case the file was never originally Lotus.  Not sure how the option was set.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>When user entered a date:  5/29/07  it was automatically changed into a formula.  The resulting number, 0.024630542,<br />
when date formatted, ended up with a date format of Jan00.  The problem was that the Transition Formula Entry option was set in the Tools, Options, Transition tab.  Unchecking this option fixed the problem.  The setting was designed to transition Lotus users into Excel, however in this case the file was never originally Lotus.  Not sure how the option was set.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brett</title>
		<link>http://www.dailydoseofexcel.com/archives/2006/03/29/read-the-manual/#comment-19973</link>
		<dc:creator>Brett</dc:creator>
		<pubDate>Wed, 21 Jun 2006 12:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1383#comment-19973</guid>
		<description>&lt;p&gt;Response 29 should read View...Toolbars...Customize...Options tab of Customize dialogue box. Sorry about that.&lt;/p&gt;
&lt;p&gt;Brett&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Response 29 should read View&#8230;Toolbars&#8230;Customize&#8230;Options tab of Customize dialogue box. Sorry about that.</p>
<p>Brett</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie Collins</title>
		<link>http://www.dailydoseofexcel.com/archives/2006/03/29/read-the-manual/#comment-19428</link>
		<dc:creator>Jamie Collins</dc:creator>
		<pubDate>Fri, 07 Apr 2006 09:13:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1383#comment-19428</guid>
		<description>&lt;p&gt;Dianne Butterworth: &quot;Number Precision = 15: first encountered after users had entered hundreds of 16-digit credit card numbers and found that the last digit had been changed to 0 on all of them.&quot;&lt;/p&gt;
&lt;p&gt;Wrong data type: a credit card number is fixed-width text! &lt;/p&gt;
&lt;p&gt;But I take you point and would add: all numerics = double precision floating point (the only fixed point type is CURRENCY, with scale limited to four).&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Dianne Butterworth: &#8220;Number Precision = 15: first encountered after users had entered hundreds of 16-digit credit card numbers and found that the last digit had been changed to 0 on all of them.&#8221;</p>
<p>Wrong data type: a credit card number is fixed-width text! </p>
<p>But I take you point and would add: all numerics = double precision floating point (the only fixed point type is CURRENCY, with scale limited to four).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dianne Butterworth</title>
		<link>http://www.dailydoseofexcel.com/archives/2006/03/29/read-the-manual/#comment-19420</link>
		<dc:creator>Dianne Butterworth</dc:creator>
		<pubDate>Thu, 06 Apr 2006 20:06:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1383#comment-19420</guid>
		<description>&lt;p&gt;Number Precision = 15: first encountered after users had entered hundreds of 16-digit credit card numbers and found that the last digit had been changed to 0 on all of them. Not fun.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Number Precision = 15: first encountered after users had entered hundreds of 16-digit credit card numbers and found that the last digit had been changed to 0 on all of them. Not fun.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brett</title>
		<link>http://www.dailydoseofexcel.com/archives/2006/03/29/read-the-manual/#comment-19351</link>
		<dc:creator>Brett</dc:creator>
		<pubDate>Fri, 31 Mar 2006 20:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1383#comment-19351</guid>
		<description>&lt;p&gt;Always show full menues&lt;br&gt;
View...Menues...customize...&lt;/p&gt;
&lt;p&gt;Thanks,&lt;br&gt;
Brett&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Always show full menues<br />
View&#8230;Menues&#8230;customize&#8230;</p>
<p>Thanks,<br />
Brett</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brett</title>
		<link>http://www.dailydoseofexcel.com/archives/2006/03/29/read-the-manual/#comment-19350</link>
		<dc:creator>Brett</dc:creator>
		<pubDate>Fri, 31 Mar 2006 20:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1383#comment-19350</guid>
		<description>&lt;p&gt;John,&lt;/p&gt;
&lt;p&gt;Make sure &#039;Always show full menus&#039; is selected.&lt;/p&gt;
&lt;p&gt;My kingdom for this option&#039;s location (disclosure: very small kingdom)! I use the keyboard almost exclusively and commands not in the custom short menus won&#039;t respond to mnemonic key strokes. Drives me nuts!!&lt;/p&gt;
&lt;p&gt;Thanks,&lt;br&gt;
Brett&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>John,</p>
<p>Make sure &#8216;Always show full menus&#8217; is selected.</p>
<p>My kingdom for this option&#8217;s location (disclosure: very small kingdom)! I use the keyboard almost exclusively and commands not in the custom short menus won&#8217;t respond to mnemonic key strokes. Drives me nuts!!</p>
<p>Thanks,<br />
Brett</p>
]]></content:encoded>
	</item>
</channel>
</rss>

