<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Excel as a Really Bad Database</title>
	<atom:link href="http://www.dailydoseofexcel.com/archives/2007/08/01/excel-as-a-really-bad-database/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dailydoseofexcel.com/archives/2007/08/01/excel-as-a-really-bad-database/</link>
	<description>Daily posts of Excel tips…and other stuff</description>
	<lastBuildDate>Thu, 09 Feb 2012 23:42:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Nancy Liebross</title>
		<link>http://www.dailydoseofexcel.com/archives/2007/08/01/excel-as-a-really-bad-database/#comment-48293</link>
		<dc:creator>Nancy Liebross</dc:creator>
		<pubDate>Sun, 25 Jul 2010 15:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1705#comment-48293</guid>
		<description>&lt;p&gt;Spire.XLS can do this well, I recommanded it, which support excel 97 ~ 2010 without office ole automation, very easy to use and performance hight.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.e-iceblue.com/Introduce/excel-for-net-introduce.html&quot; rel=&quot;nofollow&quot;&gt;http://www.e-iceblue.com/Introduce/excel-for-net-introduce.html&lt;/a&gt;&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Spire.XLS can do this well, I recommanded it, which support excel 97 ~ 2010 without office ole automation, very easy to use and performance hight.</p>
<p><a href="http://www.e-iceblue.com/Introduce/excel-for-net-introduce.html" rel="nofollow">http://www.e-iceblue.com/Introduce/excel-for-net-introduce.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barba</title>
		<link>http://www.dailydoseofexcel.com/archives/2007/08/01/excel-as-a-really-bad-database/#comment-31402</link>
		<dc:creator>Barba</dc:creator>
		<pubDate>Fri, 21 Mar 2008 12:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1705#comment-31402</guid>
		<description>&lt;p&gt;There are better ways to Read/Write XLS/CSV/HTML/XLSX files than Excel Automation (http://www.gemboxsoftware.com/GBSpreadsheet.htm). You can use our Free Spreadsheet .NET Component (http://www.gemboxsoftware.com/GBSpreadsheetFree.htm) even in your commercial applications.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>There are better ways to Read/Write XLS/CSV/HTML/XLSX files than Excel Automation (<a href="http://www.gemboxsoftware.com/GBSpreadsheet.htm" rel="nofollow">http://www.gemboxsoftware.com/GBSpreadsheet.htm</a>). You can use our Free Spreadsheet .NET Component (<a href="http://www.gemboxsoftware.com/GBSpreadsheetFree.htm" rel="nofollow">http://www.gemboxsoftware.com/GBSpreadsheetFree.htm</a>) even in your commercial applications.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Duncan</title>
		<link>http://www.dailydoseofexcel.com/archives/2007/08/01/excel-as-a-really-bad-database/#comment-26508</link>
		<dc:creator>Andy Duncan</dc:creator>
		<pubDate>Fri, 17 Aug 2007 02:38:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1705#comment-26508</guid>
		<description>&lt;p&gt;to solve this problem take a look at this:&lt;br&gt;
&lt;a href=&quot;http://boardwalktech.com&quot; rel=&quot;nofollow&quot;&gt;http://boardwalktech.com&lt;/a&gt;&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>to solve this problem take a look at this:<br />
<a href="http://boardwalktech.com" rel="nofollow">http://boardwalktech.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dick Kusleika</title>
		<link>http://www.dailydoseofexcel.com/archives/2007/08/01/excel-as-a-really-bad-database/#comment-26163</link>
		<dc:creator>Dick Kusleika</dc:creator>
		<pubDate>Fri, 03 Aug 2007 19:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1705#comment-26163</guid>
		<description>&lt;p&gt;Colin, et al:  I have many fish to fry, and this is a small one.  That&#039;s why I didn&#039;t invest more than 5 minutes in it.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Colin, et al:  I have many fish to fry, and this is a small one.  That&#8217;s why I didn&#8217;t invest more than 5 minutes in it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colin Banfield</title>
		<link>http://www.dailydoseofexcel.com/archives/2007/08/01/excel-as-a-really-bad-database/#comment-26161</link>
		<dc:creator>Colin Banfield</dc:creator>
		<pubDate>Fri, 03 Aug 2007 16:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1705#comment-26161</guid>
		<description>&lt;p&gt;Dick,&lt;/p&gt;
&lt;p&gt;Why not simply use ADO to write and read records to a single Excel file (which can remain closed when you read or write records)?  Am I missing something?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Dick,</p>
<p>Why not simply use ADO to write and read records to a single Excel file (which can remain closed when you read or write records)?  Am I missing something?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Wilson</title>
		<link>http://www.dailydoseofexcel.com/archives/2007/08/01/excel-as-a-really-bad-database/#comment-26148</link>
		<dc:creator>John Wilson</dc:creator>
		<pubDate>Fri, 03 Aug 2007 04:36:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1705#comment-26148</guid>
		<description>&lt;p&gt;The entire reason for my existence in my current job is a workbook (actually, many) that is absolutely screaming to be a database (FoxPro, preferably, if I ever get the time to convert everything).&lt;br&gt;
I do use John&#039;s XL4 macro in a few places but I find it easier (and quicker) to just import my main &quot;database&quot; into a sheet on each of my dependent workbooks when necessary. Not pretty, but it works (for me).&lt;br&gt;
Question.....&lt;br&gt;
In the latest and greatest Excel version (which I may never have a use for), did MS ever get the VLookup function on a closed workbook to ever match the incredible speed (compared to Excel) that Lotus does in 123)?&lt;br&gt;
That feature alone would be enough to make me an upgrade convert, eliminate my need for my inefficient &quot;import&quot; process, get rid of my scattered XL4 macros (and thank you, John. That XL4 routine does come in handy) and maybe stop me from wishing that I had started my whole project in FoxPro.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>The entire reason for my existence in my current job is a workbook (actually, many) that is absolutely screaming to be a database (FoxPro, preferably, if I ever get the time to convert everything).<br />
I do use John&#8217;s XL4 macro in a few places but I find it easier (and quicker) to just import my main &#8220;database&#8221; into a sheet on each of my dependent workbooks when necessary. Not pretty, but it works (for me).<br />
Question&#8230;..<br />
In the latest and greatest Excel version (which I may never have a use for), did MS ever get the VLookup function on a closed workbook to ever match the incredible speed (compared to Excel) that Lotus does in 123)?<br />
That feature alone would be enough to make me an upgrade convert, eliminate my need for my inefficient &#8220;import&#8221; process, get rid of my scattered XL4 macros (and thank you, John. That XL4 routine does come in handy) and maybe stop me from wishing that I had started my whole project in FoxPro.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jan</title>
		<link>http://www.dailydoseofexcel.com/archives/2007/08/01/excel-as-a-really-bad-database/#comment-26132</link>
		<dc:creator>Jan</dc:creator>
		<pubDate>Thu, 02 Aug 2007 10:28:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1705#comment-26132</guid>
		<description>&lt;p&gt;I think my point is &quot;You Can, but you Shouldn&#039;t&quot;.&lt;/p&gt;
&lt;p&gt;Today it is only 30 files, tomorrow it will be all of them, as soon as &quot;they&quot; (the luddites and philistines) have seen what data is available.  The day after that someone will save one of the files as Excel 97 and create some bizzare problem with a french installation and you will end up with VRAI and FAUX in the columns in place of TRUE and FALSE, and then the day after that some one will insert a column in the file having managed to open it up in some convoluted way.  What if you want to add columns? do you extend all of the files by one column?  What if there is an older version withouth this field in the headings?  Will your ADO command still work without the header row still work?  All of this has happened to me already.  Bite the bullet and get the data from the central location with data types and indexes and scalability.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I think my point is &#8220;You Can, but you Shouldn&#8217;t&#8221;.</p>
<p>Today it is only 30 files, tomorrow it will be all of them, as soon as &#8220;they&#8221; (the luddites and philistines) have seen what data is available.  The day after that someone will save one of the files as Excel 97 and create some bizzare problem with a french installation and you will end up with VRAI and FAUX in the columns in place of TRUE and FALSE, and then the day after that some one will insert a column in the file having managed to open it up in some convoluted way.  What if you want to add columns? do you extend all of the files by one column?  What if there is an older version withouth this field in the headings?  Will your ADO command still work without the header row still work?  All of this has happened to me already.  Bite the bullet and get the data from the central location with data types and indexes and scalability.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam</title>
		<link>http://www.dailydoseofexcel.com/archives/2007/08/01/excel-as-a-really-bad-database/#comment-26126</link>
		<dc:creator>Sam</dc:creator>
		<pubDate>Thu, 02 Aug 2007 06:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1705#comment-26126</guid>
		<description>&lt;p&gt;Dick,&lt;/p&gt;
&lt;p&gt;You dont need to open a file to read or write. Just use ADO&lt;br&gt;
You dont have to to depend on the XL4 macro command either its relatively slower.&lt;/p&gt;
&lt;p&gt;If data is stored in a structured way it doest matter whether it is stored in an Access file or an Excel file or in a Text file&lt;/p&gt;
&lt;p&gt;The key thing is structured storage.&lt;/p&gt;
&lt;p&gt;Sam&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Dick,</p>
<p>You dont need to open a file to read or write. Just use ADO<br />
You dont have to to depend on the XL4 macro command either its relatively slower.</p>
<p>If data is stored in a structured way it doest matter whether it is stored in an Access file or an Excel file or in a Text file</p>
<p>The key thing is structured storage.</p>
<p>Sam</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jan</title>
		<link>http://www.dailydoseofexcel.com/archives/2007/08/01/excel-as-a-really-bad-database/#comment-26119</link>
		<dc:creator>Jan</dc:creator>
		<pubDate>Wed, 01 Aug 2007 23:57:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1705#comment-26119</guid>
		<description>&lt;p&gt;Chuck it into a database and build a simple extraction spreadsheet for when they want to review it in Excel.&lt;br&gt;
I refuse to try to solve this problem in this way I have tried and it only creates more problems for yourself, you are only encouraging the luddites to believe they might have been correct.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Chuck it into a database and build a simple extraction spreadsheet for when they want to review it in Excel.<br />
I refuse to try to solve this problem in this way I have tried and it only creates more problems for yourself, you are only encouraging the luddites to believe they might have been correct.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fzz</title>
		<link>http://www.dailydoseofexcel.com/archives/2007/08/01/excel-as-a-really-bad-database/#comment-26118</link>
		<dc:creator>fzz</dc:creator>
		<pubDate>Wed, 01 Aug 2007 23:10:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydoseofexcel.com/?p=1705#comment-26118</guid>
		<description>&lt;p&gt;Looks like I forgot to mention importing the text file in TEMP.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Looks like I forgot to mention importing the text file in TEMP.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

