<?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"
	>
<channel>
	<title>Comments on: Excel Scripting Question</title>
	<atom:link href="http://nslog.com/2006/04/23/excel_scripting_question/feed" rel="self" type="application/rss+xml" />
	<link>http://nslog.com/2006/04/23/excel_scripting_question</link>
	<description>The Weblog of Erik J. Barzeski</description>
	<pubDate>Tue, 14 Oct 2008 16:09:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Kevin Hillabolt</title>
		<link>http://nslog.com/2006/04/23/excel_scripting_question#comment-18671</link>
		<dc:creator>Kevin Hillabolt</dc:creator>
		<pubDate>Mon, 24 Apr 2006 21:57:00 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2006/04/23/excel_scripting_question/#comment-18671</guid>
		<description>It is ugly and very painful, but Excel fully supports VBA (Visual Basic for Applications). I'm not sure if Office for Mac supports VBA the same as Windows. YMMV.

Without to much effort, one could craft a little VB code to export each of the sheets as a text file. In the Windows environment, you could probably even reference a component (DLL) to handle the FTP portion as well.

A brief sample of code is available here: &lt;a href="http://www.tek-tips.com/viewthread.cfm?qid=1210651&#38;page=8"&gt;http://www.tek-tips.com/viewthread.cfm?qid=1210651&#38;page=8&lt;/a&gt;

&lt;i&gt;Note that the sample page only exports the current active sheet. You would have to include additional logic to handle multiple sheets as you mentioned...&lt;/i&gt;
</description>
		<content:encoded><![CDATA[<p>It is ugly and very painful, but Excel fully supports VBA (Visual Basic for Applications). I'm not sure if Office for Mac supports VBA the same as Windows. YMMV.</p>
<p>Without to much effort, one could craft a little VB code to export each of the sheets as a text file. In the Windows environment, you could probably even reference a component (DLL) to handle the FTP portion as well.</p>
<p>A brief sample of code is available here: <a href="http://www.tek-tips.com/viewthread.cfm?qid=1210651&amp;page=8">http://www.tek-tips.com/viewthread.cfm?qid=1210651&amp;page=8</a></p>
<p><i>Note that the sample page only exports the current active sheet. You would have to include additional logic to handle multiple sheets as you mentioned...</i></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik J. Barzeski</title>
		<link>http://nslog.com/2006/04/23/excel_scripting_question#comment-18670</link>
		<dc:creator>Erik J. Barzeski</dc:creator>
		<pubDate>Mon, 24 Apr 2006 15:31:59 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2006/04/23/excel_scripting_question/#comment-18670</guid>
		<description>Dave, you're missing the point. They want to use Excel because a lot of the same people keep the same groups, so moving columns and rows around in Excel is much easier than doing so in text. And no, save as HTML is NOT an option in the least for more than obvious reasons.</description>
		<content:encoded><![CDATA[<p>Dave, you're missing the point. They want to use Excel because a lot of the same people keep the same groups, so moving columns and rows around in Excel is much easier than doing so in text. And no, save as HTML is NOT an option in the least for more than obvious reasons.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave'ola</title>
		<link>http://nslog.com/2006/04/23/excel_scripting_question#comment-18669</link>
		<dc:creator>Dave'ola</dc:creator>
		<pubDate>Mon, 24 Apr 2006 15:29:08 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2006/04/23/excel_scripting_question/#comment-18669</guid>
		<description>It might be easier to have them continue to use the TXT file and if they want to put it into an Excel file, convert *from* the TXT to Excel (instead of the other way around).  Nowadays, the copy on the web tends to be *the* master copy; when not, it tends to be neglected and outdated.

I suppose (worst case) you could have them simply do File -&#62; Save as HTML (I believe Excel has some version of this functionality in recent versions) and then upload that via FTP.</description>
		<content:encoded><![CDATA[<p>It might be easier to have them continue to use the TXT file and if they want to put it into an Excel file, convert *from* the TXT to Excel (instead of the other way around).  Nowadays, the copy on the web tends to be *the* master copy; when not, it tends to be neglected and outdated.</p>
<p>I suppose (worst case) you could have them simply do File -&gt; Save as HTML (I believe Excel has some version of this functionality in recent versions) and then upload that via <a href="http://FTP" >http://FTP</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://nslog.com/2006/04/23/excel_scripting_question#comment-18668</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Mon, 24 Apr 2006 14:09:03 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2006/04/23/excel_scripting_question/#comment-18668</guid>
		<description>If they're using a new version of MS Office, Office files are now (or can easily be) XML files.  If that's the case, XSLT could be useful here.</description>
		<content:encoded><![CDATA[<p>If they're using a new version of MS Office, Office files are now (or can easily be) XML files.  If that's the case, XSLT could be useful here.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
