﻿<?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: 3 approaches to avoid complex off-sheet references</title>
	<atom:link href="http://www.fimodo.com/2009/08/3-approaches-to-avoid-complex-off-sheet-references/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fimodo.com/2009/08/3-approaches-to-avoid-complex-off-sheet-references/</link>
	<description>Financial Modelling Experts sharing their knowledge</description>
	<lastBuildDate>Mon, 05 Dec 2011 21:58:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Rickard Wärnelid</title>
		<link>http://www.fimodo.com/2009/08/3-approaches-to-avoid-complex-off-sheet-references/comment-page-1/#comment-190</link>
		<dc:creator>Rickard Wärnelid</dc:creator>
		<pubDate>Mon, 30 Nov 2009 08:23:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.fimodo.com/?p=301#comment-190</guid>
		<description>Hi John,

I agree with your first comment that it is often used in combination with Export Areas but don&#039;t think it adds much value (but an awful lot of unnecessary Excel code!)

One of the strongest features of the philosophy behind FAST modeling standard is the simplicity (check out http://www.fast-modeling.net/) which is to a large extent achieved by a disciplined avoidance (or simplification) of off-sheet links. If you are looking for a financial modelling training course in London then Financial mechanics (http://www.fi-mech.com/) should definitely be on your shortlist. The methodology is pretty similar the financial modelling methodology preached by Navigator Project Finance (http://www.navigatorPF.com) with the main difference that Fi-Mech are more focused on productivity and Navigator are more focused on transaction presentation.

In regards to row-anchoring for subsequent copying, yes, I like it. It is just a shame it looks so bad…. Colour-coding, hm, same argument…. Both methods are great for the developer but will probably not improve the chances of getting an investment-committee across the line…. From a model audit perspective though it opens up a lot of interesting questions, like ‘this line should be blue but is read – is that an ‘error?’ 

Maybe we should generate some Fi-mech screenshots and put up on Fimodo to provide readers with a better understanding of what I have tried to explain?</description>
		<content:encoded><![CDATA[<p>Hi John,</p>
<p>I agree with your first comment that it is often used in combination with Export Areas but don&#8217;t think it adds much value (but an awful lot of unnecessary Excel code!)</p>
<p>One of the strongest features of the philosophy behind FAST modeling standard is the simplicity (check out <a href="http://www.fast-modeling.net/)" rel="nofollow">http://www.fast-modeling.net/)</a> which is to a large extent achieved by a disciplined avoidance (or simplification) of off-sheet links. If you are looking for a financial modelling training course in London then Financial mechanics (<a href="http://www.fi-mech.com/" rel="nofollow">http://www.fi-mech.com/</a>) should definitely be on your shortlist. The methodology is pretty similar the financial modelling methodology preached by Navigator Project Finance (<a href="http://www.navigatorPF.com" rel="nofollow">http://www.navigatorPF.com</a>) with the main difference that Fi-Mech are more focused on productivity and Navigator are more focused on transaction presentation.</p>
<p>In regards to row-anchoring for subsequent copying, yes, I like it. It is just a shame it looks so bad…. Colour-coding, hm, same argument…. Both methods are great for the developer but will probably not improve the chances of getting an investment-committee across the line…. From a model audit perspective though it opens up a lot of interesting questions, like ‘this line should be blue but is read – is that an ‘error?’ </p>
<p>Maybe we should generate some Fi-mech screenshots and put up on Fimodo to provide readers with a better understanding of what I have tried to explain?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Richter</title>
		<link>http://www.fimodo.com/2009/08/3-approaches-to-avoid-complex-off-sheet-references/comment-page-1/#comment-189</link>
		<dc:creator>John Richter</dc:creator>
		<pubDate>Sun, 29 Nov 2009 16:02:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.fimodo.com/?p=301#comment-189</guid>
		<description>Rickard,

Well described as always - as you&#039;d expect nothing in it that I would disagree with, and I think you&#039;ve captured the primary alternatives.  On the &#039;imports at the top&#039; Alternative 2, I would also note that I see folks put a summary of exports at the bottom of the source worksheet from time to time, though we feel this has then the weakness of daisy chaining.

Not sure &#039;tailored approach&#039; captures the concept of your recommended alternative No. 3.  To the extent you don&#039;t want to broadcast this as the F1F9 or FAST Modeling Standard, understandable, probably more descriptive to refer to it as &#039;only have off-sheet references as links placed proximately to formulas, never directly in formulas&#039; -- clearly more than a mouthful : -).

Opportunity to hear from you as well what you think about row-anchoring the off-sheet links (for subsequent copying) and/or what you think about color conventions in this regard?</description>
		<content:encoded><![CDATA[<p>Rickard,</p>
<p>Well described as always &#8211; as you&#8217;d expect nothing in it that I would disagree with, and I think you&#8217;ve captured the primary alternatives.  On the &#8216;imports at the top&#8217; Alternative 2, I would also note that I see folks put a summary of exports at the bottom of the source worksheet from time to time, though we feel this has then the weakness of daisy chaining.</p>
<p>Not sure &#8216;tailored approach&#8217; captures the concept of your recommended alternative No. 3.  To the extent you don&#8217;t want to broadcast this as the F1F9 or FAST Modeling Standard, understandable, probably more descriptive to refer to it as &#8216;only have off-sheet references as links placed proximately to formulas, never directly in formulas&#8217; &#8212; clearly more than a mouthful : -).</p>
<p>Opportunity to hear from you as well what you think about row-anchoring the off-sheet links (for subsequent copying) and/or what you think about color conventions in this regard?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rickard Wärnelid</title>
		<link>http://www.fimodo.com/2009/08/3-approaches-to-avoid-complex-off-sheet-references/comment-page-1/#comment-187</link>
		<dc:creator>Rickard Wärnelid</dc:creator>
		<pubDate>Thu, 26 Nov 2009 06:03:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.fimodo.com/?p=301#comment-187</guid>
		<description>Thanks Sourav, it has all been updated to F1F9 now. Thanks for spotting this.</description>
		<content:encoded><![CDATA[<p>Thanks Sourav, it has all been updated to F1F9 now. Thanks for spotting this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sourav Gangawat</title>
		<link>http://www.fimodo.com/2009/08/3-approaches-to-avoid-complex-off-sheet-references/comment-page-1/#comment-186</link>
		<dc:creator>Sourav Gangawat</dc:creator>
		<pubDate>Wed, 25 Nov 2009 12:16:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.fimodo.com/?p=301#comment-186</guid>
		<description>I was just reading the said article, and in the section &quot;avoid multi-level Linking - daisy chains&quot;. 

There is a typo in using the company name  F1F9. 

It is &#039;F1F9&#039; and not &#039;F1F19&#039;.

Can you please update the article for the same.</description>
		<content:encoded><![CDATA[<p>I was just reading the said article, and in the section &#8220;avoid multi-level Linking &#8211; daisy chains&#8221;. </p>
<p>There is a typo in using the company name  F1F9. </p>
<p>It is &#8216;F1F9&#8242; and not &#8216;F1F19&#8242;.</p>
<p>Can you please update the article for the same.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

