<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Convert a large Access table into Excel files</title>
	<link>http://www.terminally-incoherent.com/blog/2006/04/05/convert-a-large-access-table-into-excel-files/</link>
	<description>Utterly random, incoherent and disjointed rants and ramblings...</description>
	<pubDate>Sat, 22 Nov 2008 13:00:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Microdude</title>
		<link>http://www.terminally-incoherent.com/blog/2006/04/05/convert-a-large-access-table-into-excel-files/#comment-10316</link>
		<pubDate>Sat, 04 Oct 2008 01:05:21 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2006/04/05/convert-a-large-access-table-into-excel-files/#comment-10316</guid>
					<description>An Access table can be put into Excel, there is a decent thread on it here http://www.nettechguide.com/forums/showthread.php?t=2237723</description>
		<content:encoded><![CDATA[<p>An Access table can be put into Excel, there is a decent thread on it here <a href="http://www.nettechguide.com/forums/showthread.php?t=2237723" rel="nofollow">http://www.nettechguide.com/forums/showthread.php?t=2237723</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Luke Maciak</title>
		<link>http://www.terminally-incoherent.com/blog/2006/04/05/convert-a-large-access-table-into-excel-files/#comment-9180</link>
		<pubDate>Fri, 30 May 2008 14:58:12 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2006/04/05/convert-a-large-access-table-into-excel-files/#comment-9180</guid>
					<description>Well, it might mean that the number of colums in the tables combined is greater than the total number of columns you are allowed to have in Excel. I'm not sure how to get around that. :(</description>
		<content:encoded><![CDATA[<p>Well, it might mean that the number of colums in the tables combined is greater than the total number of columns you are allowed to have in Excel. I&#8217;m not sure how to get around that. <img src="http://www.terminally-incoherent.com/blog/wp-includes/images/smilies/icon_sad.gif" alt="(" class="wp-smiley" />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Kasy</title>
		<link>http://www.terminally-incoherent.com/blog/2006/04/05/convert-a-large-access-table-into-excel-files/#comment-9178</link>
		<pubDate>Fri, 30 May 2008 14:32:33 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2006/04/05/convert-a-large-access-table-into-excel-files/#comment-9178</guid>
					<description>Hi, 

I'm trying to export 22 multi linked (on to many realtionship) tables into excel. It keeps saying there are too many defined fields. Would you be able to help at all?

Thanks

Kasy</description>
		<content:encoded><![CDATA[<p>Hi, </p>
<p>I&#8217;m trying to export 22 multi linked (on to many realtionship) tables into excel. It keeps saying there are too many defined fields. Would you be able to help at all?</p>
<p>Thanks</p>
<p>Kasy
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Luke Maciak</title>
		<link>http://www.terminally-incoherent.com/blog/2006/04/05/convert-a-large-access-table-into-excel-files/#comment-6420</link>
		<pubDate>Thu, 04 Oct 2007 13:38:56 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2006/04/05/convert-a-large-access-table-into-excel-files/#comment-6420</guid>
					<description>You are right. You can set up your access file for querying with ODBC in windows. Then you can use DBD::ODBC driver for DBI to connect. :)</description>
		<content:encoded><![CDATA[<p>You are right. You can set up your access file for querying with ODBC in windows. Then you can use DBD::ODBC driver for DBI to connect. <img src="http://www.terminally-incoherent.com/blog/wp-includes/images/smilies/icon_smile.gif" alt=")" class="wp-smiley" />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: ths</title>
		<link>http://www.terminally-incoherent.com/blog/2006/04/05/convert-a-large-access-table-into-excel-files/#comment-6412</link>
		<pubDate>Thu, 04 Oct 2007 06:05:35 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2006/04/05/convert-a-large-access-table-into-excel-files/#comment-6412</guid>
					<description>Access has some sort of SQL query feature. Why not use a perl script to export chunks of data from each enumerated table, obeying the $ffff limit?</description>
		<content:encoded><![CDATA[<p>Access has some sort of SQL query feature. Why not use a perl script to export chunks of data from each enumerated table, obeying the $ffff limit?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Luke</title>
		<link>http://www.terminally-incoherent.com/blog/2006/04/05/convert-a-large-access-table-into-excel-files/#comment-4754</link>
		<pubDate>Mon, 11 Jun 2007 21:01:20 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2006/04/05/convert-a-large-access-table-into-excel-files/#comment-4754</guid>
					<description>Vicki, the only thing I could do was to export each Access table into a tab-separated text file (it's one of the options in the export menu), then split that file into sizable chunks, and then import each chunk as an excel worksheet. There is just no other way to do this.

Also if the tables cross reference each-other you may need to do some joins and etc. Either way, it's to much work.

You might want to explain to your supervisors that each Excel worksheet can only have 65,536 rows, and that each table in the database contains n rows so  even in the best case scenario they would the data in a very fragmented form. They will be familiar with the excel limits - all they have to do is to open Excel and scroll down till the end.

Give them an estimate of how long would it take to do, and how many excel files it would take.

I would suggest figuring out what data they want out of that file, and design some queries that will generate appropriate reports for them - then export those into Excel. Chances are they actually need only a fraction of this data for whatever they are doing.

Good luck.</description>
		<content:encoded><![CDATA[<p>Vicki, the only thing I could do was to export each Access table into a tab-separated text file (it&#8217;s one of the options in the export menu), then split that file into sizable chunks, and then import each chunk as an excel worksheet. There is just no other way to do this.</p>
<p>Also if the tables cross reference each-other you may need to do some joins and etc. Either way, it&#8217;s to much work.</p>
<p>You might want to explain to your supervisors that each Excel worksheet can only have 65,536 rows, and that each table in the database contains n rows so  even in the best case scenario they would the data in a very fragmented form. They will be familiar with the excel limits - all they have to do is to open Excel and scroll down till the end.</p>
<p>Give them an estimate of how long would it take to do, and how many excel files it would take.</p>
<p>I would suggest figuring out what data they want out of that file, and design some queries that will generate appropriate reports for them - then export those into Excel. Chances are they actually need only a fraction of this data for whatever they are doing.</p>
<p>Good luck.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: vicki</title>
		<link>http://www.terminally-incoherent.com/blog/2006/04/05/convert-a-large-access-table-into-excel-files/#comment-4753</link>
		<pubDate>Mon, 11 Jun 2007 20:31:59 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2006/04/05/convert-a-large-access-table-into-excel-files/#comment-4753</guid>
					<description>wow, i got exactly the same request at work and im having exactly the same problems.  i was trying to find a program online that might convert it but i havent had any luck.  so what exactly do you do if you dont mind me asking?  the other thing about the built in export on access is that it took like an hour for it to do it and i couldnt touch my computer during that time or it would freeze.  this is the worst task ever, but unlike you, i have about 2000 tables that are just like the one that you had.  please help! thanks!</description>
		<content:encoded><![CDATA[<p>wow, i got exactly the same request at work and im having exactly the same problems.  i was trying to find a program online that might convert it but i havent had any luck.  so what exactly do you do if you dont mind me asking?  the other thing about the built in export on access is that it took like an hour for it to do it and i couldnt touch my computer during that time or it would freeze.  this is the worst task ever, but unlike you, i have about 2000 tables that are just like the one that you had.  please help! thanks!
</p>
]]></content:encoded>
				</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 1.713 seconds -->
