<?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>Microsoft Access Team Blog : Performance</title><link>http://blogs.msdn.com/access/archive/tags/Performance/default.aspx</link><description>Tags: Performance</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Use late binding to improve the performance of tabbed forms</title><link>http://blogs.msdn.com/access/archive/2009/12/09/use-late-binding-to-improve-the-performance-of-tabbed-forms.aspx</link><pubDate>Wed, 09 Dec 2009 18:03:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9934709</guid><dc:creator>cdowns</dc:creator><slash:comments>11</slash:comments><comments>http://blogs.msdn.com/access/comments/9934709.aspx</comments><wfw:commentRss>http://blogs.msdn.com/access/commentrss.aspx?PostID=9934709</wfw:commentRss><description>&lt;p&gt;&lt;strong&gt;Luke Chung, President and Founder of FMS, Inc., has written and presented a wide range of topics related to Access over the years. In addition to their many Access related products, FMS offers a wealth of great Access &lt;/strong&gt;&lt;a href="http://www.fmsinc.com/tpapers/index.html"&gt;&lt;strong&gt;papers&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt;, &lt;/strong&gt;&lt;a href="http://www.fmsinc.com/free/tips.html"&gt;&lt;strong&gt;tips&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt;, and &lt;/strong&gt;&lt;a href="http://www.fmsinc.com/videos/index.asp"&gt;&lt;strong&gt;video&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt; on their site.&lt;/strong&gt;&lt;/p&gt;  &lt;p&gt;If you use the Tab Control to pack a lot of controls onto a form, here is a great tip to make the form load more quickly. The secret is in keeping most of the controls unbound until you need them. For example, on the form shown below, you could keep the controls on the &lt;strong&gt;Address&lt;/strong&gt;, &lt;strong&gt;Telephone&lt;/strong&gt;, and &lt;strong&gt;Other info&lt;/strong&gt; tabs unbound until you click the tabs.&lt;/p&gt;  &lt;h6&gt;&lt;a href="http://blogs.msdn.com/blogfiles/access/WindowsLiveWriter/Uselatebindingtoimprovetheperformanceoft_8D82/3_2.jpg"&gt;&lt;img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="A tab control on a form" border="0" alt="A tab control on a form" src="http://blogs.msdn.com/blogfiles/access/WindowsLiveWriter/Uselatebindingtoimprovetheperformanceoft_8D82/3_thumb.jpg" width="428" height="204" /&gt;&lt;/a&gt;&lt;/h6&gt;  &lt;p&gt;&lt;a href="http://www.fmsinc.com/microsoftaccess/Performance/Forms/LateBinding.asp" target="_blank"&gt;Check out this tip on the FMS site!&lt;/a&gt;&lt;/p&gt;  &lt;h6&gt;Become a guest blogger on the Access Team Blog! Send your Power Tips to Chris and Mike at &lt;a href="mailto:accpower@microsoft.com"&gt;accpower@microsoft.com&lt;/a&gt;.&lt;/h6&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9934709" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/access/archive/tags/User+Interface/default.aspx">User Interface</category><category domain="http://blogs.msdn.com/access/archive/tags/Form/default.aspx">Form</category><category domain="http://blogs.msdn.com/access/archive/tags/Power+Tips/default.aspx">Power Tips</category><category domain="http://blogs.msdn.com/access/archive/tags/Performance/default.aspx">Performance</category></item><item><title>3 new articles available on MSDN</title><link>http://blogs.msdn.com/access/archive/2009/10/05/3-new-articles-available-on-msdn.aspx</link><pubDate>Mon, 05 Oct 2009 18:40:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9903283</guid><dc:creator>cdowns</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/access/comments/9903283.aspx</comments><wfw:commentRss>http://blogs.msdn.com/access/commentrss.aspx?PostID=9903283</wfw:commentRss><description>&lt;p&gt;MSDN writer Sal Ricciardi alerted us to the availability of 3 new articles on MSDN, two written by Luke Chung of &lt;a href="http://www.fmsinc.com/" target="_blank"&gt;FMS Inc.&lt;/a&gt;, and one co-written by Luke Chung and Dan Haught. &lt;/p&gt;  &lt;table border="1" cellspacing="0" cellpadding="2" width="459"&gt;&lt;tbody&gt;     &lt;tr&gt;       &lt;td valign="top" width="321"&gt;&lt;strong&gt;Title&lt;/strong&gt;&lt;/td&gt;        &lt;td valign="top" width="136"&gt;&lt;strong&gt;Author(s)&lt;/strong&gt;&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td valign="top" width="321"&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/dd942824.aspx " target="_blank"&gt;Performance Tips To Speed Up Your Access 2007 Database&lt;/a&gt;&lt;/td&gt;        &lt;td valign="top" width="136"&gt;Luke Chung and Dan Haught&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td valign="top" width="321"&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ee358847.aspx " target="_blank"&gt;Error Handling and Debugging Tips for Access 2007, VB, and VBA&lt;/a&gt;&lt;/td&gt;        &lt;td valign="top" width="136"&gt;Luke Chung&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td valign="top" width="321"&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/dd638587.aspx " target="_blank"&gt;Tips and Techniques for Queries in Access 2007&lt;/a&gt;&lt;/td&gt;        &lt;td valign="top" width="136"&gt;Luke Chung&lt;/td&gt;     &lt;/tr&gt;   &lt;/tbody&gt;&lt;/table&gt;  &lt;p&gt;Definitely bookmark these for future reference!&lt;/p&gt;  &lt;h6&gt;Send your Power Tips to Mike and Chris at &lt;a href="mailto:accpower@microsoft.com"&gt;accpower@microsoft.com&lt;/a&gt;.&lt;/h6&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9903283" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/access/archive/tags/Code/default.aspx">Code</category><category domain="http://blogs.msdn.com/access/archive/tags/Power+Tips/default.aspx">Power Tips</category><category domain="http://blogs.msdn.com/access/archive/tags/Performance/default.aspx">Performance</category><category domain="http://blogs.msdn.com/access/archive/tags/Queries/default.aspx">Queries</category><category domain="http://blogs.msdn.com/access/archive/tags/Debugging/default.aspx">Debugging</category></item><item><title>Users love fast apps</title><link>http://blogs.msdn.com/access/archive/2009/07/01/users-love-fast-apps.aspx</link><pubDate>Thu, 02 Jul 2009 06:29:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9812759</guid><dc:creator>Clint Covington</dc:creator><slash:comments>6</slash:comments><comments>http://blogs.msdn.com/access/comments/9812759.aspx</comments><wfw:commentRss>http://blogs.msdn.com/access/commentrss.aspx?PostID=9812759</wfw:commentRss><description>&lt;p&gt;There is a &lt;a href="http://radar.oreilly.com/2009/07/velocity-making-your-site-fast.html "&gt;good article&lt;/a&gt; that recaps the recent &lt;a href="http://en.oreilly.com/velocity2009"&gt;O’Reilly Velocity 2009&lt;/a&gt; conference on web performance and operations. I particularly liked this quote:&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;&lt;em&gt;Phil Dixon, from &lt;/em&gt;&lt;a href="http://www.shopzilla.com/"&gt;&lt;em&gt;Shopzilla&lt;/em&gt;&lt;/a&gt;&lt;em&gt;, had the most takeaway statistics about the impact of performance on the bottom line. A year-long performance redesign resulted in a 5 second speed up (from ~7 seconds to ~2 seconds). This resulted in a 25% increase in page views, a 7-12% increase in revenue, and a 50% reduction in hardware. This last point shows the win-win of performance improvements, increasing revenue while driving down operating costs.&lt;/em&gt;&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;There are probably fewer ways to increase satisfaction from people that use your application than good old block and tackle performance improvements. Here is a &lt;a href="http://office.microsoft.com/en-us/access/HP051874531033.aspx"&gt;help article&lt;/a&gt; with lots of useful ideas to explore making your app faster.&lt;/p&gt;  &lt;p&gt;Do you have success stories of delighting customers by making your app faster? What techniques did you employ? &lt;/p&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9812759" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/access/archive/tags/Power+Tips/default.aspx">Power Tips</category><category domain="http://blogs.msdn.com/access/archive/tags/Performance/default.aspx">Performance</category></item><item><title>Fast-Fast-Fast Compact and Repair of Large Databases!</title><link>http://blogs.msdn.com/access/archive/2009/06/01/fast-fast-fast-compact-and-repair-of-large-databases.aspx</link><pubDate>Mon, 01 Jun 2009 18:43:12 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9678353</guid><dc:creator>cdowns</dc:creator><slash:comments>15</slash:comments><comments>http://blogs.msdn.com/access/comments/9678353.aspx</comments><wfw:commentRss>http://blogs.msdn.com/access/commentrss.aspx?PostID=9678353</wfw:commentRss><description>&lt;h5&gt;Today’s guest blogger is Michael Groh, co-author of the popular &lt;a href="http://www.amazon.com/Access-2007-Bible-Michael-Groh/dp/0470046732/"&gt;Access 2007 Bible&lt;/a&gt;.&lt;/h5&gt;  &lt;p&gt;I think it's safe to say that anyone who's worked with really large Access databases (like, in excess of 50 or 100 megabytes) has encountered slow compact and repair cycles. My favorite anecdote in this regard is a very large database managed by an old buddy of mine. His database has several large tables containing more than 20 million rows each. When it's time to compact and repair, he starts it up on Friday before leaving work, and the operation is &lt;i&gt;usually&lt;/i&gt; complete by Monday morning.&lt;/p&gt;  &lt;p&gt;Not to worry! What Steve really needs to do is break up his humongous ACCDB file into multiple ACCDBs, each containing just one of his big tables, then link the individual database files to a central database. The central database, of course, would contain the forms, reports, queries, and other database. He'll find that compacting the constituent databases (as sequential operations) goes much faster than compacting the one big database.&lt;/p&gt;  &lt;p&gt;Also, one advantage of breaking big databases up into smaller pieces is that, in the event of database corruption, the corruption will affect only one portion of the total database. Presumably, the database system is easily restored by replacing the corrupted database from a backup.&lt;/p&gt;  &lt;h6&gt;Have an Access Power Tip that you want to share? Send it to Mike and Chris at &lt;a href="mailto:accpower@microsoft.com"&gt;accpower@microsoft.com&lt;/a&gt;. &lt;/h6&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9678353" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/access/archive/tags/Power+Tips/default.aspx">Power Tips</category><category domain="http://blogs.msdn.com/access/archive/tags/Performance/default.aspx">Performance</category></item></channel></rss>