<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Don't forget about the &amp;quot;A&amp;quot; in &amp;quot;VBA&amp;quot;!</title><link>http://blogs.msdn.com/excel/archive/2008/10/17/don-t-forget-about-the-a-in-vba.aspx</link><description>Today's author, Stephane Viot, a Program Manager in the Office Global Experience Platform team, reflects on how leveraging application features could help speed up the development of your VBA solutions, while improving their performance. Often -but hopefully</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>infoblog &amp;raquo; Don&amp;#8217;t forget about the &amp;#8220;A&amp;#8221; in &amp;#8220;VBA&amp;#8221;!</title><link>http://blogs.msdn.com/excel/archive/2008/10/17/don-t-forget-about-the-a-in-vba.aspx#9003552</link><pubDate>Fri, 17 Oct 2008 22:16:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9003552</guid><dc:creator>infoblog &amp;raquo; Don&amp;#8217;t forget about the &amp;#8220;A&amp;#8221; in &amp;#8220;VBA&amp;#8221;!</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://blog.a-foton.ru/index.php/2008/10/17/dont-forget-about-the-a-in-vba/"&gt;http://blog.a-foton.ru/index.php/2008/10/17/dont-forget-about-the-a-in-vba/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Don't forget about the "A" in "VBA"!</title><link>http://blogs.msdn.com/excel/archive/2008/10/17/don-t-forget-about-the-a-in-vba.aspx#9003630</link><pubDate>Fri, 17 Oct 2008 23:25:52 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9003630</guid><dc:creator>Jon Peltier</dc:creator><description>&lt;p&gt;This is a very good thing to remind programmers of. Unfortunately, many programmers are as unfamiliar with the parent application as they are with the business domain they are programming for.&lt;/p&gt;
&lt;p&gt;Excel is a fine platform for application development, because it has an extensive calculation engine and a decent presentation layer. But I have seen Excel VBA &amp;quot;solutions&amp;quot; (I hesitate to use that word) which reproduce many built-in features of Excel, usually much less efficiently.&lt;/p&gt;
</description></item><item><title>re: Don't forget about the "A" in "VBA"!</title><link>http://blogs.msdn.com/excel/archive/2008/10/17/don-t-forget-about-the-a-in-vba.aspx#9003639</link><pubDate>Fri, 17 Oct 2008 23:28:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9003639</guid><dc:creator>Mike Woodhouse</dc:creator><description>&lt;p&gt;Very true. The &amp;quot;dive for VBA&amp;quot; thing is symptomatic of the user who's trying to make a little knowledge go too far.&lt;/p&gt;
&lt;p&gt;Throw in a good understanding of indirection, offset, lookups, match/index and array formulae, and there's an astonishing amount one can achieve without ever getting to the VBE. And once that's mastered, I reckon the user will know when to go to code.&lt;/p&gt;
&lt;p&gt;I have to confess to having written a VBA &amp;quot;RangeJoin&amp;quot; function, that wraps Join(), mind you.&lt;/p&gt;
</description></item><item><title>re: Don't forget about the "A" in "VBA"!</title><link>http://blogs.msdn.com/excel/archive/2008/10/17/don-t-forget-about-the-a-in-vba.aspx#9003949</link><pubDate>Sat, 18 Oct 2008 02:53:58 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9003949</guid><dc:creator>dermotb</dc:creator><description>&lt;p&gt;Stephane, VBA is faster than you may think. I can read in and sort unique values from 60,000 cells, in just 0.2 seconds. &lt;/p&gt;
&lt;p&gt;This is because VBA can create unique lists extremely quickly using Collections, and readily available QuickSort code handles the sorting. &lt;/p&gt;
&lt;p&gt;So VBA can replicate the functionality of the add-in without using any Excel functions. That doesn't mean it's a better solution, naturally, but let's not undersell VBA! &lt;/p&gt;
</description></item><item><title>re: Don't forget about the "A" in "VBA"!</title><link>http://blogs.msdn.com/excel/archive/2008/10/17/don-t-forget-about-the-a-in-vba.aspx#9007606</link><pubDate>Mon, 20 Oct 2008 18:11:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9007606</guid><dc:creator>Stephane Viot</dc:creator><description>&lt;p&gt;Thank you all for your comments.&lt;/p&gt;
&lt;p&gt;Dermot, I guess my post is as much about performance as it is about not &amp;quot;reinventing the wheel&amp;quot;. Your observation as well as Dany's excellent article (&amp;quot;What is the fastest way to scan a large range in Excel?&amp;quot; at &amp;nbsp;&lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/excel/archive/2008/10/03/what-is-the-fastest-way-to-scan-a-large-range-in-excel.aspx"&gt;http://blogs.msdn.com/excel/archive/2008/10/03/what-is-the-fastest-way-to-scan-a-large-range-in-excel.aspx&lt;/a&gt;) clearly show that VBA can be extremely fast... when used properly. The other benefits of taking advantage of the application OM usually are more compact code, less complex code, and (in my case :-)) less buggy code. Think about the number of developers and testers behind the OM...&lt;/p&gt;
</description></item><item><title>re: Don't forget about the "A" in "VBA"!</title><link>http://blogs.msdn.com/excel/archive/2008/10/17/don-t-forget-about-the-a-in-vba.aspx#9012498</link><pubDate>Thu, 23 Oct 2008 08:23:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9012498</guid><dc:creator>gkeramidas</dc:creator><description>&lt;p&gt;please don't forget about the speed in excel 2003 and port it over to excel 2007 in sp2. excel code execution in excel 2007 is atrocious and you should be ashamed of yourselves.&lt;/p&gt;
</description></item></channel></rss>