<?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>nandeshwar.info &#187; Error messages</title>
	<atom:link href="http://nandeshwar.info/category/error-messages/feed/" rel="self" type="application/rss+xml" />
	<link>http://nandeshwar.info</link>
	<description></description>
	<lastBuildDate>Mon, 12 Dec 2011 21:33:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Microsoft query in Excel and Case statement</title>
		<link>http://nandeshwar.info/2010/04/15/microsoft-query-in-excel-and-case-statement/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=microsoft-query-in-excel-and-case-statement</link>
		<comments>http://nandeshwar.info/2010/04/15/microsoft-query-in-excel-and-case-statement/#comments</comments>
		<pubDate>Thu, 15 Apr 2010 19:49:08 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Error messages]]></category>
		<category><![CDATA[excel]]></category>
		<category><![CDATA[MS query]]></category>
		<category><![CDATA[SQL]]></category>

		<guid isPermaLink="false">http://nandeshwar.info/?p=323</guid>
		<description><![CDATA[It is frustrating that I need to pull the data from SQL server using complex queries and then format it in Excel to &#8221;prettify&#8221; the data. Thankfully, I can use the Microsoft query in Excel to get the data from SQL server and create a table or a PivotTable. Today, I encountered a problem with [...]]]></description>
			<content:encoded><![CDATA[<p>It is frustrating that I need to pull the data from SQL server using complex queries and then format it in Excel to &#8221;prettify&#8221; the data. Thankfully, I can use the Microsoft query in Excel to get the data from SQL server and create a table or a PivotTable. Today, I encountered a problem with the case statement.</p>
<p>Although my syntax was right, MS Query kept throwing exception about the CASE statement. I read some discussions on-line, and some people had the wrong syntax, such as including the alias of the case statement in the group by statement. I did not have that problem. Finally, I found the solution: It was the order by clause. I was using the alias of the case statement in the order by clause. I removed it and the query ran just fine.</p>
]]></content:encoded>
			<wfw:commentRss>http://nandeshwar.info/2010/04/15/microsoft-query-in-excel-and-case-statement/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The search key was not found in any record in Access</title>
		<link>http://nandeshwar.info/2009/09/15/the-search-key-was-not-found-in-any-record-in-access/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=the-search-key-was-not-found-in-any-record-in-access</link>
		<comments>http://nandeshwar.info/2009/09/15/the-search-key-was-not-found-in-any-record-in-access/#comments</comments>
		<pubDate>Tue, 15 Sep 2009 20:07:58 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Access]]></category>
		<category><![CDATA[Error messages]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[Microsoft Jet]]></category>

		<guid isPermaLink="false">http://nandeshwar.info/?p=290</guid>
		<description><![CDATA[Well, I got this error message today while I was trying to import a text file: &#8220;The search key was not found in any record&#8221; After some research, I found that either it was a bug caused by Microsoft Jet 4.0 Service Pack or it was the size of the database (should be not greater [...]]]></description>
			<content:encoded><![CDATA[<p>Well, I got this error message today while I was trying to import a text file:</p>
<blockquote><p>&#8220;The search key was not found in any record&#8221;</p></blockquote>
<p>After some research, I found that either it was a bug caused by <a href="http://support.microsoft.com/kb/301474">Microsoft Jet 4.0 Service Pack</a> or it was the size of the database (should be not greater than 2GB). It turned out to be the later one. I fixed this problem by compacting and resizing the database. In Access 2007, you click on the Office Button (Top Left Corner), then Manage &gt; Compact and Repair Database.</p>
]]></content:encoded>
			<wfw:commentRss>http://nandeshwar.info/2009/09/15/the-search-key-was-not-found-in-any-record-in-access/feed/</wfw:commentRss>
		<slash:comments>20</slash:comments>
		</item>
		<item>
		<title>Access to the VB project is not trusted</title>
		<link>http://nandeshwar.info/2009/04/24/access-to-the-vb-project-is-not-trusted/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=access-to-the-vb-project-is-not-trusted</link>
		<comments>http://nandeshwar.info/2009/04/24/access-to-the-vb-project-is-not-trusted/#comments</comments>
		<pubDate>Fri, 24 Apr 2009 14:42:37 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Error messages]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[excel]]></category>
		<category><![CDATA[VBA]]></category>

		<guid isPermaLink="false">http://nandeshwar.info/?p=197</guid>
		<description><![CDATA[I was trying to enable an add-in for Excel 2007, and I kept getting this error: Access to the VB project is not trusted You can turn this message off by going to Developer tab in the ribbon and then clicking on the Macro security button, and checking the check box for &#8220;Trust access to [...]]]></description>
			<content:encoded><![CDATA[<p>I was trying to enable an add-in for Excel 2007, and I kept getting this error:</p>
<blockquote><p>Access to the VB project is not trusted</p></blockquote>
<p>You can turn this message off by going to Developer tab in the ribbon and then clicking on the Macro security button, and checking the check box for &#8220;Trust access to the VBA project object model.&#8221;</p>
<p>A word of caution: be wary of the add-ins/projects that need VBA access. Don&#8217;t allow any project/add-in with VBA access, unless you know its exact purpose or the author of that project.</p>
]]></content:encoded>
			<wfw:commentRss>http://nandeshwar.info/2009/04/24/access-to-the-vb-project-is-not-trusted/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The data on the Clipboard is damaged, so Microsoft Office Access can&#8217;t paste it.</title>
		<link>http://nandeshwar.info/2009/04/06/the-data-on-the-clipboard-is-damaged-so-microsoft-office-access-cant-paste-it/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=the-data-on-the-clipboard-is-damaged-so-microsoft-office-access-cant-paste-it</link>
		<comments>http://nandeshwar.info/2009/04/06/the-data-on-the-clipboard-is-damaged-so-microsoft-office-access-cant-paste-it/#comments</comments>
		<pubDate>Mon, 06 Apr 2009 14:41:57 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Error messages]]></category>
		<category><![CDATA[Access]]></category>

		<guid isPermaLink="false">http://nandeshwar.info/?p=181</guid>
		<description><![CDATA[This is a new one for me. One good thing working with Excel and Access is the Copy/Paste ease between them. I usually paste data from Excel to Access for these two reasons: Create tables in Access (for small tables) Paste Field names: either in a table or in the import specs form When I [...]]]></description>
			<content:encoded><![CDATA[<p>This is a new one for me. One good thing working with Excel and Access is the Copy/Paste ease between them. I usually paste data from Excel to Access for these two reasons:</p>
<ol>
<li>Create tables in Access (for small tables)</li>
<li>Paste Field names: either in a table or in the import specs form</li>
</ol>
<p>When I am importing data of the web, usually they have field names and data types given that page, so it makes sense to import that table in Excel (using Import from Web option), and then copy the field names and directly paste them the import specs form in Access. However, I kept running in this error today, which <a href="http://support.microsoft.com/kb/958437">MS acknowledged and provided a solution</a>, caused due to a security patch.</p>
<p>I used a workaround to paste those field names: copy and paste the data in a text file, and the again copy and paste it in Excel.</p>
<p><strong>Solution Update</strong>: <a href="http://nandeshwar.info/2009/04/06/the-data-on-the-clipboard-is-damaged-so-microsoft-office-access-cant-paste-it/?preview=true&amp;preview_id=181&amp;preview_nonce=a7eb2a8fce#comment-1316"><span id="commentauthor-1316">Colleen</span></a> provided one more MS KB number to fix this problem. So, there are two KB articles which acknowledge this problem:</p>
<p>KB967699: <a href="http://support.microsoft.com/kb/967699">http://support.microsoft.com/kb/967699</a></p>
<p>KB958437: <a href="http://support.microsoft.com/kb/958437">http://support.microsoft.com/kb/958437</a></p>
]]></content:encoded>
			<wfw:commentRss>http://nandeshwar.info/2009/04/06/the-data-on-the-clipboard-is-damaged-so-microsoft-office-access-cant-paste-it/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Access Export to Excel (2007)</title>
		<link>http://nandeshwar.info/2009/03/02/access-export-to-excel-2007/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=access-export-to-excel-2007</link>
		<comments>http://nandeshwar.info/2009/03/02/access-export-to-excel-2007/#comments</comments>
		<pubDate>Mon, 02 Mar 2009 18:54:28 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Access]]></category>
		<category><![CDATA[Error messages]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[export]]></category>

		<guid isPermaLink="false">http://nandeshwar.info/?p=134</guid>
		<description><![CDATA[When I tried to export a table/query from Access 2007 to Excel 2007, I was getting this annoying error: You selected more records than can be copied onto the Clipboard at one time. Divide the records into two or more groups, and then copy and paste one group at a time. The maximum number of [...]]]></description>
			<content:encoded><![CDATA[<p>When I tried to export a table/query from Access 2007 to Excel 2007, I was getting this annoying error:</p>
<blockquote><p>You selected more records than can be copied onto the Clipboard at one time.  Divide the records into two or more groups, and then copy and paste one group at a time. The maximum number of records you can paste at one time is approximately 65,000.</p>
<div id="attachment_135" class="wp-caption alignnone" style="width: 310px"><img class="size-medium wp-image-135" title="Access 2007 Export to Excel Error" src="http://nandeshwar.info/wp-content/uploads/2009/03/accesserror-300x77.jpg" alt="Access 2007 Export to Excel Error" width="300" height="77" /><p class="wp-caption-text">Access 2007 Export to Excel Error</p></div></blockquote>
<p>I was unable to understand the reason, because I thought Excel 2007 did not limit number of rows to 65,536. It turns out however that it is the clipboard limitation.</p>
<p><strong>Solution:</strong> If you check off the &#8220;export data with formatting and layout&#8221; option, Access exports successfully.</p>
<p>You can export successfully using Transferspreadsheet (VBA) option too.</p>
<p><a title="MS KB" href="http://support.microsoft.com/kb/924681" target="_self">Here is the KB from MS</a>.</p>
<p><strong>Solution Update:</strong>Thanks to <a href="http://nandeshwar.info/2009/03/02/access-export-to-excel-2007/#comment-1753">Brett</a>, it looks like that only if you export table/query using right click &gt; Export and have the checkbox cleared, then Access will export succesfully. That is what I always do, and it works for me. I have never tried External data option for exporting.</p>
]]></content:encoded>
			<wfw:commentRss>http://nandeshwar.info/2009/03/02/access-export-to-excel-2007/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
	</channel>
</rss>

