<?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: Learn to Program Excel to Become a Better Monarch Modeler</title>
	<atom:link href="http://ExcelWithMonarch.com/xlreport/learn-to-program-excel-to-become-a-better-monarch-modeler/feed" rel="self" type="application/rss+xml" />
	<link>http://ExcelWithMonarch.com/xlreport/learn-to-program-excel-to-become-a-better-monarch-modeler</link>
	<description>Stop working for your data. Make your data work for you.</description>
	<lastBuildDate>Thu, 26 Apr 2012 01:47:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Sandy</title>
		<link>http://ExcelWithMonarch.com/xlreport/learn-to-program-excel-to-become-a-better-monarch-modeler/comment-page-1#comment-20284</link>
		<dc:creator>Sandy</dc:creator>
		<pubDate>Fri, 19 Feb 2010 00:16:04 +0000</pubDate>
		<guid isPermaLink="false">http://ExcelWithMonarch.com/xlreport/learn-to-program-excel-to-become-a-better-monarch-modeler#comment-20284</guid>
		<description>I like how you worded that Nick!

Seriously, it really is amazing how quickly one can build powerful stand-alone applications with Excel once you&#039;re got a bit a library of routines and classes and such.

Lately I&#039;ve been building far more summaries and project exports than I&#039;d done previously for inclusion in Excel dashboard application. It makes for not only quick development but also fantastically easy periodic updating.</description>
		<content:encoded><![CDATA[<p>I like how you worded that Nick!</p>
<p>Seriously, it really is amazing how quickly one can build powerful stand-alone applications with Excel once you&#8217;re got a bit a library of routines and classes and such.</p>
<p>Lately I&#8217;ve been building far more summaries and project exports than I&#8217;d done previously for inclusion in Excel dashboard application. It makes for not only quick development but also fantastically easy periodic updating.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://ExcelWithMonarch.com/xlreport/learn-to-program-excel-to-become-a-better-monarch-modeler/comment-page-1#comment-20279</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Thu, 18 Feb 2010 23:37:11 +0000</pubDate>
		<guid isPermaLink="false">http://ExcelWithMonarch.com/xlreport/learn-to-program-excel-to-become-a-better-monarch-modeler#comment-20279</guid>
		<description>As you know, I LOVE programming with Excel. I&#039;ve taken the basic routines from the Monarch Programming Guide from V4 or V5 I believe and created my own VBA Class. It has evolved tremendously since then.  My Excel programs are what&#039;s known as &#039;dictator&#039; apps. They take over Excel exclusively, hiding menus, toolbars and other Excel elements. If you were to see one of them, you wouldn&#039;t even know you were working in Excel.
Because of this and the years I&#039;ve put into this, I&#039;ve created a base shell for my Excel apps. This has made development a breeze. The basic interface is usually already done for me. The only UI change is the user input form. All my real development is in creating the correct filters and summaries in Monarch and in VBA the core processing of what needs to be accomplished. Depending on the process I find that I can usually get 50-80% of the data analyzed in Monarch, and Excel is used just for formatting.
For me VBA/automation is the only way to Excel with Monarch.</description>
		<content:encoded><![CDATA[<p>As you know, I LOVE programming with Excel. I&#8217;ve taken the basic routines from the Monarch Programming Guide from V4 or V5 I believe and created my own VBA Class. It has evolved tremendously since then.  My Excel programs are what&#8217;s known as &#8216;dictator&#8217; apps. They take over Excel exclusively, hiding menus, toolbars and other Excel elements. If you were to see one of them, you wouldn&#8217;t even know you were working in Excel.<br />
Because of this and the years I&#8217;ve put into this, I&#8217;ve created a base shell for my Excel apps. This has made development a breeze. The basic interface is usually already done for me. The only UI change is the user input form. All my real development is in creating the correct filters and summaries in Monarch and in VBA the core processing of what needs to be accomplished. Depending on the process I find that I can usually get 50-80% of the data analyzed in Monarch, and Excel is used just for formatting.<br />
For me VBA/automation is the only way to Excel with Monarch.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

