<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Comedy support</title>
	<atom:link href="http://smurfonspreadsheets.wordpress.com/2010/06/16/comedy-support/feed/" rel="self" type="application/rss+xml" />
	<link>http://smurfonspreadsheets.wordpress.com/2010/06/16/comedy-support/</link>
	<description>Simon Murphy on professional spreadsheet development stuff</description>
	<lastBuildDate>Thu, 18 Apr 2013 08:42:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Harlan Grove</title>
		<link>http://smurfonspreadsheets.wordpress.com/2010/06/16/comedy-support/#comment-15771</link>
		<dc:creator><![CDATA[Harlan Grove]]></dc:creator>
		<pubDate>Thu, 17 Jun 2010 16:34:47 +0000</pubDate>
		<guid isPermaLink="false">http://smurfonspreadsheets.wordpress.com/?p=2267#comment-15771</guid>
		<description><![CDATA[You want comedy? About 14 years ago the company I was working for at the time paid for me to travel from California to New Jersey to diagnose a problem east coast users were having with a model I was maintaining at the time. Turned out that IT had upgraded east coast offices to Lotus 123 Release 5 before the rest of the country. I was still using Release 4.

So what was the problem? The model read text files into particular ranges in the workbook. Release 4 treated formfeed characters in the text files as just another oddball character, displaying ♀ when it came across one. Release 5 OTOH would create new worksheets whenever it came across formfeed characters, so each printout page would be in a separate worksheet. Since the workbook was protected, the macro died before importing the needed information, which was after the first formfeed character.

So roughly US$1,500 travel expenses and 2 days of my time just because IT for whatever reason upgraded software on a piecemeal basis and didn&#039;t think of testing the newer 123 version against any existing spreadsheet models.

Gotta love maintenance!]]></description>
		<content:encoded><![CDATA[<p>You want comedy? About 14 years ago the company I was working for at the time paid for me to travel from California to New Jersey to diagnose a problem east coast users were having with a model I was maintaining at the time. Turned out that IT had upgraded east coast offices to Lotus 123 Release 5 before the rest of the country. I was still using Release 4.</p>
<p>So what was the problem? The model read text files into particular ranges in the workbook. Release 4 treated formfeed characters in the text files as just another oddball character, displaying ♀ when it came across one. Release 5 OTOH would create new worksheets whenever it came across formfeed characters, so each printout page would be in a separate worksheet. Since the workbook was protected, the macro died before importing the needed information, which was after the first formfeed character.</p>
<p>So roughly US$1,500 travel expenses and 2 days of my time just because IT for whatever reason upgraded software on a piecemeal basis and didn&#8217;t think of testing the newer 123 version against any existing spreadsheet models.</p>
<p>Gotta love maintenance!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JP</title>
		<link>http://smurfonspreadsheets.wordpress.com/2010/06/16/comedy-support/#comment-15770</link>
		<dc:creator><![CDATA[JP]]></dc:creator>
		<pubDate>Thu, 17 Jun 2010 12:54:05 +0000</pubDate>
		<guid isPermaLink="false">http://smurfonspreadsheets.wordpress.com/?p=2267#comment-15770</guid>
		<description><![CDATA[Sounds like the &quot;simple&quot; problem Bob was having:

http://msmvps.com/blogs/xldynamic/archive/2010/06/09/thicker-than-a-length-of-4be2.aspx]]></description>
		<content:encoded><![CDATA[<p>Sounds like the &#8220;simple&#8221; problem Bob was having:</p>
<p><a href="http://msmvps.com/blogs/xldynamic/archive/2010/06/09/thicker-than-a-length-of-4be2.aspx" rel="nofollow">http://msmvps.com/blogs/xldynamic/archive/2010/06/09/thicker-than-a-length-of-4be2.aspx</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://smurfonspreadsheets.wordpress.com/2010/06/16/comedy-support/#comment-15768</link>
		<dc:creator><![CDATA[Rob]]></dc:creator>
		<pubDate>Wed, 16 Jun 2010 21:41:05 +0000</pubDate>
		<guid isPermaLink="false">http://smurfonspreadsheets.wordpress.com/?p=2267#comment-15768</guid>
		<description><![CDATA[No. But I&#039;ve just worked on a project where the user insisted on keeping every sheet permanently in Page Break Preview mode. Odd, and incredibly distracting, but that&#039;s the way they worked. I&#039;ve a feeling that somewhere a bit further up the food chain was a manager who insisted on seeing everything only on paper, and company culture had subsequently elevated &#039;looking good when printed out&#039; to a fetish.
And I had to write some extensions to my normal Sheet_BeforeRightClick routines in order for them to work correctly. Which was OK - they feel a lot more robust now.]]></description>
		<content:encoded><![CDATA[<p>No. But I&#8217;ve just worked on a project where the user insisted on keeping every sheet permanently in Page Break Preview mode. Odd, and incredibly distracting, but that&#8217;s the way they worked. I&#8217;ve a feeling that somewhere a bit further up the food chain was a manager who insisted on seeing everything only on paper, and company culture had subsequently elevated &#8216;looking good when printed out&#8217; to a fetish.<br />
And I had to write some extensions to my normal Sheet_BeforeRightClick routines in order for them to work correctly. Which was OK &#8211; they feel a lot more robust now.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
