<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Solution Log &#124; Antonio David - NVNCBL &#187; wizard</title>
	<atom:link href="http://www.nvncbl.com/tagged/wizard/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nvncbl.com</link>
	<description>A place to log my programming solutions for future reference</description>
	<lastBuildDate>Sun, 28 Aug 2011 01:20:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>When Wizards Get in the Way</title>
		<link>http://www.nvncbl.com/2009/06/when-wizards-get-in-the-way/</link>
		<comments>http://www.nvncbl.com/2009/06/when-wizards-get-in-the-way/#comments</comments>
		<pubDate>Sun, 14 Jun 2009 17:57:07 +0000</pubDate>
		<dc:creator>Antonio</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[reporting]]></category>
		<category><![CDATA[sql]]></category>
		<category><![CDATA[stored procedure]]></category>
		<category><![CDATA[visual studio]]></category>
		<category><![CDATA[wizard]]></category>

		<guid isPermaLink="false">http://www.nvncbl.com/?p=238</guid>
		<description><![CDATA[Many of Microsoft&#8217;s development products, when given an SQL query, will try to perform all sorts of analysis and breakdowns on the query &#8212; usually in an attempt to visualize what&#8217;s going on.  When the queries become too complex (as the tend to be), they just can&#8217;t be parsed and visualized.  Furthermore, when the successful [...]]]></description>
			<content:encoded><![CDATA[<p>Many of Microsoft&#8217;s development products, when given an SQL query, will try to perform all sorts of analysis and breakdowns on the query &#8212; usually in an attempt to visualize what&#8217;s going on.  When the queries become too complex (as the tend to be), they just can&#8217;t be parsed and visualized.  Furthermore, when the successful parsing of a query is critical to one of their &#8220;wizards&#8221;, your report creation process can be brought to a standstill.</p>
<p>
<a href="http://www.nvncbl.com/wp-content/gallery/articles/wizard.jpg" title="" class="shutterset_singlepic23" >
	<img class="ngg-singlepic ngg-left" src="http://www.nvncbl.com/wp-content/gallery/cache/23__125x94_wizard.jpg" alt="wizard.jpg" title="wizard.jpg" />
</a>
Queries that have a few levels of subquery nesting, or that have UNIONs, for example, will sometimes break parsing.</p>
<p>So, if you don&#8217;t want your development tools (such as Visual Studio) to get in the way of completing a report wizard, put your SQL query in a stored procedure.  This way, your tools won&#8217;t be concerned with the nitty gritty details of your query.  You can still pass @variables to the query, and you can make changes to the query without stepping into your designer&#8217;s .rdlc files.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.nvncbl.com/2009/06/when-wizards-get-in-the-way/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

