<?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 for Schwieb</title>
	<atom:link href="http://www.schwieb.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.schwieb.com/blog</link>
	<description>Random blatherings</description>
	<lastBuildDate>Tue, 27 Jul 2010 12:35:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>Comment on Saying hello (again) to Visual Basic by John Caulfield</title>
		<link>http://www.schwieb.com/blog/2008/05/13/saying-hello-again-to-visual-basic/comment-page-3/#comment-35960</link>
		<dc:creator>John Caulfield</dc:creator>
		<pubDate>Tue, 27 Jul 2010 12:35:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35960</guid>
		<description>Ok so you can&#039;t write VBA in 2008 but can you run a macro from 2007. The macro&#039;s window certainly pops up like Excl 2007?</description>
		<content:encoded><![CDATA[<p>Ok so you can&#8217;t write VBA in 2008 but can you run a macro from 2007. The macro&#8217;s window certainly pops up like Excl 2007?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying goodbye to Visual Basic by Sonam Yadav</title>
		<link>http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/comment-page-5/#comment-35958</link>
		<dc:creator>Sonam Yadav</dc:creator>
		<pubDate>Fri, 23 Jul 2010 06:40:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/#comment-35958</guid>
		<description>Thanx, for your help. Actualy I have a excel with specific template. The excel file have a macro written in VBA attached with it. Whenever another user downloads that file that macro is executed. I want to write that same macro in applescript and attach it to excel as excel 2008 don’t have support for VB macro. Is there any way to execute macro written in applescript through excel 2008, so whenever another user download this excel file that macro written in applescript should be executed automatically and provides same functionality as macro in VBA. Please help me with this problem.

Thanx again.</description>
		<content:encoded><![CDATA[<p>Thanx, for your help. Actualy I have a excel with specific template. The excel file have a macro written in VBA attached with it. Whenever another user downloads that file that macro is executed. I want to write that same macro in applescript and attach it to excel as excel 2008 don’t have support for VB macro. Is there any way to execute macro written in applescript through excel 2008, so whenever another user download this excel file that macro written in applescript should be executed automatically and provides same functionality as macro in VBA. Please help me with this problem.</p>
<p>Thanx again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying goodbye to Visual Basic by Mackenab.com &#187; Blog Archive &#187; A Microsoft-less World?</title>
		<link>http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/comment-page-5/#comment-35957</link>
		<dc:creator>Mackenab.com &#187; Blog Archive &#187; A Microsoft-less World?</dc:creator>
		<pubDate>Thu, 15 Jul 2010 03:48:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/#comment-35957</guid>
		<description>[...] just found this post explaining in some detail why the Microsoft Mac Business Unit (MacBU) is dropping VBA support.  It [...]</description>
		<content:encoded><![CDATA[<p>[...] just found this post explaining in some detail why the Microsoft Mac Business Unit (MacBU) is dropping VBA support.  It [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying hello (again) to Visual Basic by Kate</title>
		<link>http://www.schwieb.com/blog/2008/05/13/saying-hello-again-to-visual-basic/comment-page-3/#comment-35956</link>
		<dc:creator>Kate</dc:creator>
		<pubDate>Sun, 04 Jul 2010 19:44:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35956</guid>
		<description>Agree that sales have been good, since most people don&#039;t know a macro from a mud hen and like me, run into the problem by accident. Other big thing driving sales, I would guess is that many, like me, chose to switch to Mac when the other choice was Vista. Not impressed to learn that I will have to buy the next iteration of Office to get functionality that every other version of the software previously in existence has. Not comforted to learn that Microsoft, given a choice between shipping &quot;crap&quot; now and shipping &quot;quality&quot; later, chose the former.</description>
		<content:encoded><![CDATA[<p>Agree that sales have been good, since most people don&#8217;t know a macro from a mud hen and like me, run into the problem by accident. Other big thing driving sales, I would guess is that many, like me, chose to switch to Mac when the other choice was Vista. Not impressed to learn that I will have to buy the next iteration of Office to get functionality that every other version of the software previously in existence has. Not comforted to learn that Microsoft, given a choice between shipping &#8220;crap&#8221; now and shipping &#8220;quality&#8221; later, chose the former.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying hello (again) to Visual Basic by Carl</title>
		<link>http://www.schwieb.com/blog/2008/05/13/saying-hello-again-to-visual-basic/comment-page-3/#comment-35955</link>
		<dc:creator>Carl</dc:creator>
		<pubDate>Wed, 09 Jun 2010 05:54:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35955</guid>
		<description>I have entirely different issues w/ Office 2008, which I got most importantly due to wanting access to .docx  and .xlsx  formatted documents that I sometimes receive.  My issues aren&#039;t total deal-breakers, but irritations.  

I have tons of really old documents in Word 4 and Word 5 format, even a few in Word 3.  Word 2008 doesn&#039;t open them in any easy way.  I can use the Open dialog, but then I have to figure out the path to to the file I was trying to open.  Grungy.  Or I can open &#039;em in AppleWorks via MacLinkPlus to see if the file is the right one &amp; if so, close it, &amp; go thru the above.  Also grungy.   There may be a better answer, but I&#039;ve looked &amp; don&#039;t know where it is.  Word 4 &amp; 5 didn&#039;t have macros, so I don&#039;t see why Word 2008 requires this workaround just to open a file.  (Maybe it was too embarrassing to explain to people that Word 6 w/ evil macros was the problem - I never got Word 6! - &amp; it would look bad if Word 2008 would easily open Word 5 files but not Word 6 files.) 

Word ought to open files from *all* previous versions.  Ditto for Excel &amp; PowerPoint.  This should be nearly seamless.  A few oddities are ok - for instance, if an ancient file uses ancient bitmapped fonts, it&#039;s ok to warn about that when opening the file.  Similarly, a Word 6 file w/ macros should be easily accessible but the macros don&#039;t have to work - in fact, they should be OFF by default, even if you include the capability. 

About VBA &amp; scripting:  I never used VBA.  Glad to hear it&#039;s coming back, not so much for my own use, as because VBA is essential to Excel/Mac&#039;s commercial future.  I have simple scripts in AppleWorks, and I do some fairly light scripting in FileMaker.  Haven&#039;t done much w/ Excel 08, but one project worked *really well*, much better than in Excel 98 which had been my previous version.  Remember, I don&#039;t use VBA.  PowerPoint is similarly much better in 2008 than in 98.  

I intentionally use a rather old Mac &amp; OS 10.4 so that if I have to, I can boot into OS 9.  (Yes, I&#039;m a fossil.)  On that rather old Mac (933 MHz), Word 2008 is slow to open.  Grrr.  Microsoft went thru that before w/ Word 6; Word 98 was much improved.  But something I like about my setup: I can save in my choice of .doc or .docx &amp; test .doc files w/ Word 98 to make sure others w/ old sw can open the files.      

I tried OpenOffice.  I&#039;m glad I have it handy, just in case, but I use it only when someone sends me a file that opens in it.</description>
		<content:encoded><![CDATA[<p>I have entirely different issues w/ Office 2008, which I got most importantly due to wanting access to .docx  and .xlsx  formatted documents that I sometimes receive.  My issues aren&#8217;t total deal-breakers, but irritations.  </p>
<p>I have tons of really old documents in Word 4 and Word 5 format, even a few in Word 3.  Word 2008 doesn&#8217;t open them in any easy way.  I can use the Open dialog, but then I have to figure out the path to to the file I was trying to open.  Grungy.  Or I can open &#8216;em in AppleWorks via MacLinkPlus to see if the file is the right one &amp; if so, close it, &amp; go thru the above.  Also grungy.   There may be a better answer, but I&#8217;ve looked &amp; don&#8217;t know where it is.  Word 4 &amp; 5 didn&#8217;t have macros, so I don&#8217;t see why Word 2008 requires this workaround just to open a file.  (Maybe it was too embarrassing to explain to people that Word 6 w/ evil macros was the problem &#8211; I never got Word 6! &#8211; &amp; it would look bad if Word 2008 would easily open Word 5 files but not Word 6 files.) </p>
<p>Word ought to open files from *all* previous versions.  Ditto for Excel &amp; PowerPoint.  This should be nearly seamless.  A few oddities are ok &#8211; for instance, if an ancient file uses ancient bitmapped fonts, it&#8217;s ok to warn about that when opening the file.  Similarly, a Word 6 file w/ macros should be easily accessible but the macros don&#8217;t have to work &#8211; in fact, they should be OFF by default, even if you include the capability. </p>
<p>About VBA &amp; scripting:  I never used VBA.  Glad to hear it&#8217;s coming back, not so much for my own use, as because VBA is essential to Excel/Mac&#8217;s commercial future.  I have simple scripts in AppleWorks, and I do some fairly light scripting in FileMaker.  Haven&#8217;t done much w/ Excel 08, but one project worked *really well*, much better than in Excel 98 which had been my previous version.  Remember, I don&#8217;t use VBA.  PowerPoint is similarly much better in 2008 than in 98.  </p>
<p>I intentionally use a rather old Mac &amp; OS 10.4 so that if I have to, I can boot into OS 9.  (Yes, I&#8217;m a fossil.)  On that rather old Mac (933 MHz), Word 2008 is slow to open.  Grrr.  Microsoft went thru that before w/ Word 6; Word 98 was much improved.  But something I like about my setup: I can save in my choice of .doc or .docx &amp; test .doc files w/ Word 98 to make sure others w/ old sw can open the files.      </p>
<p>I tried OpenOffice.  I&#8217;m glad I have it handy, just in case, but I use it only when someone sends me a file that opens in it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying goodbye to Visual Basic by Plymouth Design Group &#187; Blog Archive &#187; Macros For Macintosh Excel 2008 using XLM</title>
		<link>http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/comment-page-5/#comment-35954</link>
		<dc:creator>Plymouth Design Group &#187; Blog Archive &#187; Macros For Macintosh Excel 2008 using XLM</dc:creator>
		<pubDate>Tue, 08 Jun 2010 17:29:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/#comment-35954</guid>
		<description>[...]  You&#8217;ll find that VBA doesn&#8217;t work at all under Excel 2008 for Mac, because Microsoft decided to remove it.  They are pushing users toward AppleScript as an alternative scripting technology, [...]</description>
		<content:encoded><![CDATA[<p>[...]  You&#8217;ll find that VBA doesn&#8217;t work at all under Excel 2008 for Mac, because Microsoft decided to remove it.  They are pushing users toward AppleScript as an alternative scripting technology, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying hello (again) to Visual Basic by toby</title>
		<link>http://www.schwieb.com/blog/2008/05/13/saying-hello-again-to-visual-basic/comment-page-3/#comment-35950</link>
		<dc:creator>toby</dc:creator>
		<pubDate>Sat, 10 Apr 2010 20:54:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35950</guid>
		<description>Will macros VB really be back, and if so, when? 
I created hundreds of commands using 2004 for Mac, which I use in translating repetitive texts. I upgraded to 2008 when suddenly a bug in the Macros caused them to stop working completely. I have no idea why this happened - launching macros now causes word to shut down.

I have currently my first mac (powerbook G4) running Word 2004 for Mac, and it&#039;s functioning well. But the computer is about to croak, sadly. I will need to either purchase a new Word 2004, or wait for the new version.

Which is why I ask - when is it planned?

Much thanks!</description>
		<content:encoded><![CDATA[<p>Will macros VB really be back, and if so, when?<br />
I created hundreds of commands using 2004 for Mac, which I use in translating repetitive texts. I upgraded to 2008 when suddenly a bug in the Macros caused them to stop working completely. I have no idea why this happened &#8211; launching macros now causes word to shut down.</p>
<p>I have currently my first mac (powerbook G4) running Word 2004 for Mac, and it&#8217;s functioning well. But the computer is about to croak, sadly. I will need to either purchase a new Word 2004, or wait for the new version.</p>
<p>Which is why I ask &#8211; when is it planned?</p>
<p>Much thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying goodbye to Visual Basic by Eric Pettigrew</title>
		<link>http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/comment-page-5/#comment-35949</link>
		<dc:creator>Eric Pettigrew</dc:creator>
		<pubDate>Sat, 10 Apr 2010 06:18:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/#comment-35949</guid>
		<description>It would take you two years to rewrite the code? So what? It took me five years to acquire the knowledge to write applications which talked to each other in Office across Access, Excel, and Outlook, all of which use VBA.

And no one was paying me out of some corporate budget. I came to Macs late in life, but if I could, would drop the various PCs I have just because the Mac is a beautiful machine. 

The arrogance of Microsoft, with its screw the customer attitude is mind-boggling.  (you once tried to charge me £230 just to ask a question when I found a bug in Access which then you credited after you admitted it was your fault). This is just another brick in the Microsoft stonewall built with complete disregard of your customers and the work they put in to adapt your undoubtedly great parts of the package (Pivot Tables for instance) to good use.

A plague on your house.</description>
		<content:encoded><![CDATA[<p>It would take you two years to rewrite the code? So what? It took me five years to acquire the knowledge to write applications which talked to each other in Office across Access, Excel, and Outlook, all of which use VBA.</p>
<p>And no one was paying me out of some corporate budget. I came to Macs late in life, but if I could, would drop the various PCs I have just because the Mac is a beautiful machine. </p>
<p>The arrogance of Microsoft, with its screw the customer attitude is mind-boggling.  (you once tried to charge me £230 just to ask a question when I found a bug in Access which then you credited after you admitted it was your fault). This is just another brick in the Microsoft stonewall built with complete disregard of your customers and the work they put in to adapt your undoubtedly great parts of the package (Pivot Tables for instance) to good use.</p>
<p>A plague on your house.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying goodbye to Visual Basic by John C.</title>
		<link>http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/comment-page-5/#comment-35948</link>
		<dc:creator>John C.</dc:creator>
		<pubDate>Sun, 14 Mar 2010 16:57:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/#comment-35948</guid>
		<description>I&#039;ve read this explanation twice now, and basically it boils down to &quot;I couldn&#039;t be bothered&quot;. Pathetic. You have removed basic functionality from a program and claim that this is an improvement I should be grateful for? Why not remove the ability to create plots, that would actually be much less destructive for many many users than what you have actually done. I have a huge number of alternatives, better alternatives, if I want to create pretty plots and pro-quality spreadsheet graphics. I have no alternative program to run all my macros (which include some incredibly complex and powerful data processing plugins). Doesn&#039;t it make you feel sick knowing that you have spent years creating a useless program? Doesn&#039;t it crush pride to know that you have wasted years of your life? You say that most macros are portable to AppleScript, but that only goes to show just how little you appear to understand about the way that many people use macros, and just how many highly complex macros are in daily use by a huge number of people around the world. What you have now is just a substandard finance-only spreadsheet program, and you have killed Excel as a serious piece of scientific software. So it would have been some work for you. Diddums. That&#039;s what you are paid for. Have you any comprehension of just how much money your decision has cost users around the world, how much time, how much stress? So your manager was close to crying, awww... I have actually SEEN users cry when they realise just how crap Excel 2008 is. The chart wizard is fucked. The macros are fucked sideways. And you claim it is improved? Moron.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve read this explanation twice now, and basically it boils down to &#8220;I couldn&#8217;t be bothered&#8221;. Pathetic. You have removed basic functionality from a program and claim that this is an improvement I should be grateful for? Why not remove the ability to create plots, that would actually be much less destructive for many many users than what you have actually done. I have a huge number of alternatives, better alternatives, if I want to create pretty plots and pro-quality spreadsheet graphics. I have no alternative program to run all my macros (which include some incredibly complex and powerful data processing plugins). Doesn&#8217;t it make you feel sick knowing that you have spent years creating a useless program? Doesn&#8217;t it crush pride to know that you have wasted years of your life? You say that most macros are portable to AppleScript, but that only goes to show just how little you appear to understand about the way that many people use macros, and just how many highly complex macros are in daily use by a huge number of people around the world. What you have now is just a substandard finance-only spreadsheet program, and you have killed Excel as a serious piece of scientific software. So it would have been some work for you. Diddums. That&#8217;s what you are paid for. Have you any comprehension of just how much money your decision has cost users around the world, how much time, how much stress? So your manager was close to crying, awww&#8230; I have actually SEEN users cry when they realise just how crap Excel 2008 is. The chart wizard is fucked. The macros are fucked sideways. And you claim it is improved? Moron.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Leave those bits alone! by Endorphinity</title>
		<link>http://www.schwieb.com/blog/2008/08/14/leave-those-bits-alone/comment-page-1/#comment-35947</link>
		<dc:creator>Endorphinity</dc:creator>
		<pubDate>Thu, 11 Mar 2010 20:50:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=81#comment-35947</guid>
		<description>How safe would be running &quot;ditto --arch i386 Word.app Word_i.app&quot; for Office apps?</description>
		<content:encoded><![CDATA[<p>How safe would be running &#8220;ditto &#8211;arch i386 Word.app Word_i.app&#8221; for Office apps?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying goodbye to Visual Basic by Mac Office 2008 Hits Private Beta &#171; MacRumors.com</title>
		<link>http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/comment-page-5/#comment-35946</link>
		<dc:creator>Mac Office 2008 Hits Private Beta &#171; MacRumors.com</dc:creator>
		<pubDate>Wed, 03 Mar 2010 14:39:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/#comment-35946</guid>
		<description>[...] Microsoft has stated that Office 2008 will be a Universal Binary, and will bring compatibility with Office 2007 for Windows&#8217; Open XML file format. To the dismay of many corporate and cross-platform users, however, Microsoft has said that it will not be supporting Visual Basic scripting. [...]</description>
		<content:encoded><![CDATA[<p>[...] Microsoft has stated that Office 2008 will be a Universal Binary, and will bring compatibility with Office 2007 for Windows&#8217; Open XML file format. To the dismay of many corporate and cross-platform users, however, Microsoft has said that it will not be supporting Visual Basic scripting. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying hello (again) to Visual Basic by Clifford Longley</title>
		<link>http://www.schwieb.com/blog/2008/05/13/saying-hello-again-to-visual-basic/comment-page-3/#comment-35944</link>
		<dc:creator>Clifford Longley</dc:creator>
		<pubDate>Sat, 16 Jan 2010 14:32:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35944</guid>
		<description>I&#039;ve just placed an order for Mac Word 2004, having already bought Word 2008 two months ago, in order to get macros back. I had a whole suite of macros for my MS Word X, but for some reason that application will not run on the new (post October 2009) iMacs. This is not the fault of Snow Leopard by the way, as Word X (plus macros!) works perfectly on my Intel MacBook with OS 10.6.2. 
I am a journalist, editor and book author, and my needs may be slightly different from some of your other respondents, which is why I am writing this. I found macros invaluable for editing, or for tidying up imperfect text either due to my own bad typing or someone else&#039;s. I had one f-key to trigger a macro which would swap a character with the one to its right (a macro I called &quot;transpose&quot;) as this is one of the most common mistpyings (see what I mean!); I had one f-key to delete the whole word under the cursor wherever it may be, one f-key to translate Roman text instantly into italics, one to insert page numbers into a document, one that would make the first letter of a word Upper Case (and another key for vice versa), an f-key for spell check  (less necessary but I used it all the time); one to change fonts from Courier to Times Roman or back --- and so on. The joy of macros was that you worked out the sequence of things you wanted to do to the text, eg  select a letter, &quot;cut&quot; it, move one space forward, paste letter into text - and then just repeated it with the record macro command on, having designated a function key, then saved it.  Apple script just will not allow that. I am so frustrated by the lack of macros with 2008 that I am prepared to fork out for the older version, 2004, where macros still work, thank God. If I had the money to sue Microsoft I would, I&#039;m so cross!</description>
		<content:encoded><![CDATA[<p>I&#8217;ve just placed an order for Mac Word 2004, having already bought Word 2008 two months ago, in order to get macros back. I had a whole suite of macros for my MS Word X, but for some reason that application will not run on the new (post October 2009) iMacs. This is not the fault of Snow Leopard by the way, as Word X (plus macros!) works perfectly on my Intel MacBook with OS 10.6.2.<br />
I am a journalist, editor and book author, and my needs may be slightly different from some of your other respondents, which is why I am writing this. I found macros invaluable for editing, or for tidying up imperfect text either due to my own bad typing or someone else&#8217;s. I had one f-key to trigger a macro which would swap a character with the one to its right (a macro I called &#8220;transpose&#8221;) as this is one of the most common mistpyings (see what I mean!); I had one f-key to delete the whole word under the cursor wherever it may be, one f-key to translate Roman text instantly into italics, one to insert page numbers into a document, one that would make the first letter of a word Upper Case (and another key for vice versa), an f-key for spell check  (less necessary but I used it all the time); one to change fonts from Courier to Times Roman or back &#8212; and so on. The joy of macros was that you worked out the sequence of things you wanted to do to the text, eg  select a letter, &#8220;cut&#8221; it, move one space forward, paste letter into text &#8211; and then just repeated it with the record macro command on, having designated a function key, then saved it.  Apple script just will not allow that. I am so frustrated by the lack of macros with 2008 that I am prepared to fork out for the older version, 2004, where macros still work, thank God. If I had the money to sue Microsoft I would, I&#8217;m so cross!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying goodbye to Visual Basic by moe.</title>
		<link>http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/comment-page-5/#comment-35942</link>
		<dc:creator>moe.</dc:creator>
		<pubDate>Tue, 12 Jan 2010 14:19:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/#comment-35942</guid>
		<description>sorry, dann leider kein update. wäre längst geschehen. dann kann man auch numbers verwenden.</description>
		<content:encoded><![CDATA[<p>sorry, dann leider kein update. wäre längst geschehen. dann kann man auch numbers verwenden.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying hello (again) to Visual Basic by Anonymous</title>
		<link>http://www.schwieb.com/blog/2008/05/13/saying-hello-again-to-visual-basic/comment-page-3/#comment-35941</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 11 Jan 2010 08:28:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35941</guid>
		<description>PIVOT TABLES in Excel should be identical to those of Windows.  Having to drag fields onto the sheet to see the affect does not work near as well as dragging them to the &#039;input&#039; boxes that Windows uses.

Also, this situation begs the question &quot;Why don&#039;t you put the Office 2004 VBA into a service pack for those of us who bought 2008 and had to &#039;downgrade&#039;???</description>
		<content:encoded><![CDATA[<p>PIVOT TABLES in Excel should be identical to those of Windows.  Having to drag fields onto the sheet to see the affect does not work near as well as dragging them to the &#8216;input&#8217; boxes that Windows uses.</p>
<p>Also, this situation begs the question &#8220;Why don&#8217;t you put the Office 2004 VBA into a service pack for those of us who bought 2008 and had to &#8216;downgrade&#8217;???</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying goodbye to Visual Basic by The worm in the apple</title>
		<link>http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/comment-page-5/#comment-35938</link>
		<dc:creator>The worm in the apple</dc:creator>
		<pubDate>Wed, 06 Jan 2010 02:03:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/#comment-35938</guid>
		<description>[...] December 2006 Update: My attention has been drawn to an earlier post from a lead in Microsoft&#8217;s Mac Business Unit, where the removal of support for Visual Basic [...]</description>
		<content:encoded><![CDATA[<p>[...] December 2006 Update: My attention has been drawn to an earlier post from a lead in Microsoft&#8217;s Mac Business Unit, where the removal of support for Visual Basic [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying goodbye to Visual Basic by Daniela</title>
		<link>http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/comment-page-5/#comment-35937</link>
		<dc:creator>Daniela</dc:creator>
		<pubDate>Mon, 23 Nov 2009 16:11:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/#comment-35937</guid>
		<description>Do you have any other solution for us mac users? What our we supposed to tell our clients? Sorry it&#039;s just not possible?!</description>
		<content:encoded><![CDATA[<p>Do you have any other solution for us mac users? What our we supposed to tell our clients? Sorry it&#8217;s just not possible?!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying goodbye to Visual Basic by erik dörnenburg &#187; Articles &#187; How toxic is your code?</title>
		<link>http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/comment-page-5/#comment-35936</link>
		<dc:creator>erik dörnenburg &#187; Articles &#187; How toxic is your code?</dc:creator>
		<pubDate>Tue, 03 Nov 2009 02:36:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/#comment-35936</guid>
		<description>[...] time. So, naturally, I&#8217;d like to use Excel on the Mac but, alas, in its current version it does not support VBA anymore. So, unfortunately, it&#8217;s VMWare Fusion for this [...]</description>
		<content:encoded><![CDATA[<p>[...] time. So, naturally, I&#8217;d like to use Excel on the Mac but, alas, in its current version it does not support VBA anymore. So, unfortunately, it&#8217;s VMWare Fusion for this [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying goodbye to Visual Basic by matti</title>
		<link>http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/comment-page-5/#comment-35934</link>
		<dc:creator>matti</dc:creator>
		<pubDate>Sat, 24 Oct 2009 08:20:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/#comment-35934</guid>
		<description>if you wrote a serious office vba app on the mac you are nuts anyway and deserve what you got.</description>
		<content:encoded><![CDATA[<p>if you wrote a serious office vba app on the mac you are nuts anyway and deserve what you got.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Risks and Rewards by laeeq</title>
		<link>http://www.schwieb.com/blog/2008/10/23/risks-and-rewards/comment-page-1/#comment-35933</link>
		<dc:creator>laeeq</dc:creator>
		<pubDate>Wed, 21 Oct 2009 08:55:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35933</guid>
		<description>This issue is almost fixed in the latest version. Check Apple site for info.

&lt;a href=&quot;http://blog.macmasters.net&quot; rel=&quot;nofollow&quot;&gt;MacMasters&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>This issue is almost fixed in the latest version. Check Apple site for info.</p>
<p><a href="http://blog.macmasters.net" rel="nofollow">MacMasters</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying hello (again) to Visual Basic by Thomas Roll</title>
		<link>http://www.schwieb.com/blog/2008/05/13/saying-hello-again-to-visual-basic/comment-page-3/#comment-35931</link>
		<dc:creator>Thomas Roll</dc:creator>
		<pubDate>Thu, 15 Oct 2009 20:10:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35931</guid>
		<description>The fact that VBA was lost in the upgrade to 2008 was a sad event, but the big problem for me was that no SDK or interface was detailed that would enable me to provide the functionality in Excel that 2004 did.

It was not a question of there not being a particular interface (VBA) available to me, but the fact that there was NO interface available at all. Without an SDK or a detailed interface, we had no method by which to provide the functionality required by our users.

Be it XCode, VBA or a some other method - please give us an interface that we can use to extend the functionality of Excel to meet the needs we have. My requirements are not met by off-the-shelf products, and more than likely never will be. I doubt that I am alone.</description>
		<content:encoded><![CDATA[<p>The fact that VBA was lost in the upgrade to 2008 was a sad event, but the big problem for me was that no SDK or interface was detailed that would enable me to provide the functionality in Excel that 2004 did.</p>
<p>It was not a question of there not being a particular interface (VBA) available to me, but the fact that there was NO interface available at all. Without an SDK or a detailed interface, we had no method by which to provide the functionality required by our users.</p>
<p>Be it XCode, VBA or a some other method &#8211; please give us an interface that we can use to extend the functionality of Excel to meet the needs we have. My requirements are not met by off-the-shelf products, and more than likely never will be. I doubt that I am alone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying hello (again) to Visual Basic by John</title>
		<link>http://www.schwieb.com/blog/2008/05/13/saying-hello-again-to-visual-basic/comment-page-3/#comment-35916</link>
		<dc:creator>John</dc:creator>
		<pubDate>Fri, 07 Aug 2009 21:51:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35916</guid>
		<description>In the original &quot;blathering&quot;, Schweib said &quot;I’ve been told that we must have cut VB to intentionally drive users to use virtualization and Windows Office 2007 on Macs&quot;.

It may not have been intentional, but that&#039;s the only way I have been able to run Excel on my Mac and maintain compatibility with Office 2007.

It&#039;s not just the lack of VBA, it&#039;s the crippled filtering, the lack of graduated color conditional formatting, the lack of filter by color, the lack of sort by color, all features that I became dependent on in 2007.

Microsoft is in denial about the lack of compatibility, look at this page:-

http://www.microsoft.com/mac/products/office2008/why-office.mspx

&quot;Compatibility is Essential
No one likes being caught off guard, especially when the pressure’s on. That’s why it’s vital that shared documents, presentations, and spreadsheets open as they were designed—regardless of the computer or operating system.&quot;

and

&quot;Microsoft ensures that Office 2008 for Mac is forward, backward, and cross-platform compatible.&quot;

and

&quot;Office 2008 for Mac is the best option for Mac users who share documents at home, work, or at school.&quot;

The above statements are just not true.

It is my belief that the high sales rate is a result of misleading advertising.</description>
		<content:encoded><![CDATA[<p>In the original &#8220;blathering&#8221;, Schweib said &#8220;I’ve been told that we must have cut VB to intentionally drive users to use virtualization and Windows Office 2007 on Macs&#8221;.</p>
<p>It may not have been intentional, but that&#8217;s the only way I have been able to run Excel on my Mac and maintain compatibility with Office 2007.</p>
<p>It&#8217;s not just the lack of VBA, it&#8217;s the crippled filtering, the lack of graduated color conditional formatting, the lack of filter by color, the lack of sort by color, all features that I became dependent on in 2007.</p>
<p>Microsoft is in denial about the lack of compatibility, look at this page:-</p>
<p><a href="http://www.microsoft.com/mac/products/office2008/why-office.mspx" rel="nofollow">http://www.microsoft.com/mac/products/office2008/why-office.mspx</a></p>
<p>&#8220;Compatibility is Essential<br />
No one likes being caught off guard, especially when the pressure’s on. That’s why it’s vital that shared documents, presentations, and spreadsheets open as they were designed—regardless of the computer or operating system.&#8221;</p>
<p>and</p>
<p>&#8220;Microsoft ensures that Office 2008 for Mac is forward, backward, and cross-platform compatible.&#8221;</p>
<p>and</p>
<p>&#8220;Office 2008 for Mac is the best option for Mac users who share documents at home, work, or at school.&#8221;</p>
<p>The above statements are just not true.</p>
<p>It is my belief that the high sales rate is a result of misleading advertising.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying hello (again) to Visual Basic by Phillip Blue</title>
		<link>http://www.schwieb.com/blog/2008/05/13/saying-hello-again-to-visual-basic/comment-page-3/#comment-35915</link>
		<dc:creator>Phillip Blue</dc:creator>
		<pubDate>Fri, 31 Jul 2009 12:15:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35915</guid>
		<description>To all those who are disillusioned with MacBu at Microshaft I urge you to try Neo Office I did in January and I havn&#039;t looked back.  Now I have no Microsoft products in my office and my computers all seem to work better.</description>
		<content:encoded><![CDATA[<p>To all those who are disillusioned with MacBu at Microshaft I urge you to try Neo Office I did in January and I havn&#8217;t looked back.  Now I have no Microsoft products in my office and my computers all seem to work better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying hello (again) to Visual Basic by Oakland Tracy</title>
		<link>http://www.schwieb.com/blog/2008/05/13/saying-hello-again-to-visual-basic/comment-page-3/#comment-35914</link>
		<dc:creator>Oakland Tracy</dc:creator>
		<pubDate>Tue, 21 Jul 2009 00:24:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35914</guid>
		<description>&quot;This seems to me to be a strong example for the MacBU naysayers that we’re really listening to what all of our users want, and that we’re most definitely not slow-marching to some bagpiper’s funereal drone!&quot;

Put it back into Office 2008 or give me a free upgrade to the next release of Office and I&#039;ll actually believe that line.</description>
		<content:encoded><![CDATA[<p>&#8220;This seems to me to be a strong example for the MacBU naysayers that we’re really listening to what all of our users want, and that we’re most definitely not slow-marching to some bagpiper’s funereal drone!&#8221;</p>
<p>Put it back into Office 2008 or give me a free upgrade to the next release of Office and I&#8217;ll actually believe that line.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Risks and Rewards by Dan</title>
		<link>http://www.schwieb.com/blog/2008/10/23/risks-and-rewards/comment-page-1/#comment-35913</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Mon, 20 Jul 2009 16:59:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35913</guid>
		<description>You want a simple fix .... just don&#039;t combine every single palette into one global all knowing toolbox.  The formatting palette should be its own palette.  Everything else can be thrown into a second pallete (that no one will ever use).  That way you don&#039;t have to use multiple windows on a single toolbox.  

The simplest solution is usually the best solution.  If Spaces doesn&#039;t support multiple grouped windows, don&#039;t use multiple grouped windows!</description>
		<content:encoded><![CDATA[<p>You want a simple fix &#8230;. just don&#8217;t combine every single palette into one global all knowing toolbox.  The formatting palette should be its own palette.  Everything else can be thrown into a second pallete (that no one will ever use).  That way you don&#8217;t have to use multiple windows on a single toolbox.  </p>
<p>The simplest solution is usually the best solution.  If Spaces doesn&#8217;t support multiple grouped windows, don&#8217;t use multiple grouped windows!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying hello (again) to Visual Basic by Chris</title>
		<link>http://www.schwieb.com/blog/2008/05/13/saying-hello-again-to-visual-basic/comment-page-3/#comment-35912</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Thu, 16 Jul 2009 19:06:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35912</guid>
		<description>On the comment that sales were great despite lack of VB -- a lot of people (my whole department included) NEVER IMAGINED this functionality would be missing in the upgrade. Had we known, we might have reconsidered. Or, at least, opted NOT TO DELETE the old office during 08 installation app.

Issue should have been better handled.</description>
		<content:encoded><![CDATA[<p>On the comment that sales were great despite lack of VB &#8212; a lot of people (my whole department included) NEVER IMAGINED this functionality would be missing in the upgrade. Had we known, we might have reconsidered. Or, at least, opted NOT TO DELETE the old office during 08 installation app.</p>
<p>Issue should have been better handled.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Risks and Rewards by matt</title>
		<link>http://www.schwieb.com/blog/2008/10/23/risks-and-rewards/comment-page-1/#comment-35911</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Sun, 28 Jun 2009 22:08:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35911</guid>
		<description>Ok, fault-finding aside, can we expect this to be fixed (or quickly fixable) in Snow Leopard?  Sorry if this is an ignorant question, but this is the first good detailed discussion of this I&#039;ve seen-- it&#039;s just a little outside of my non-engineer competence.</description>
		<content:encoded><![CDATA[<p>Ok, fault-finding aside, can we expect this to be fixed (or quickly fixable) in Snow Leopard?  Sorry if this is an ignorant question, but this is the first good detailed discussion of this I&#8217;ve seen&#8211; it&#8217;s just a little outside of my non-engineer competence.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Risks and Rewards by Dave</title>
		<link>http://www.schwieb.com/blog/2008/10/23/risks-and-rewards/comment-page-1/#comment-35910</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Sat, 27 Jun 2009 17:48:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35910</guid>
		<description>&quot;And why the hell is there no VBA? Is it that hard?&quot;

Yeah, it is actually. I would argue that the reasons are mostly self-inflicted, but it&#039;s still a non-trivial task. If it makes you feel better, VBA support is supposed to come back in the next version (Office 2011? IDK).

http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/
http://www.schwieb.com/blog/2008/05/13/saying-hello-again-to-visual-basic/</description>
		<content:encoded><![CDATA[<p>&#8220;And why the hell is there no VBA? Is it that hard?&#8221;</p>
<p>Yeah, it is actually. I would argue that the reasons are mostly self-inflicted, but it&#8217;s still a non-trivial task. If it makes you feel better, VBA support is supposed to come back in the next version (Office 2011? IDK).</p>
<p><a href="http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/" rel="nofollow">http://www.schwieb.com/blog/2006/08/08/saying-goodbye-to-visual-basic/</a><br />
<a href="http://www.schwieb.com/blog/2008/05/13/saying-hello-again-to-visual-basic/" rel="nofollow">http://www.schwieb.com/blog/2008/05/13/saying-hello-again-to-visual-basic/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Risks and Rewards by Mojo</title>
		<link>http://www.schwieb.com/blog/2008/10/23/risks-and-rewards/comment-page-1/#comment-35909</link>
		<dc:creator>Mojo</dc:creator>
		<pubDate>Wed, 10 Jun 2009 16:24:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35909</guid>
		<description>The spaces/toolbar problem could be solved so easily. I guess there is some kind of event that is raised before/when the space changes. Just hde the toolbar or make word inactive (eg. focus finder) and it won&#039;t get moved to the next space. If you use cmd-tab to jump to another application on a different space, the toolbar doesn&#039;t get moved because the app is activated, word is deactivated and the toolbar is hidden ...

What was said about performance has nothing to do with 30000 pixels or what so ever. Sometimes I feel like being near a singularity because word is so slow. Add a picture and then wait a few seconds before it is drawn. There a plenty of other situation, where the speed just sucks. And my documents are not even big. Just admit it, the codebase is a mess. The implementation is just bad! Making such an ugly hacked toolbar ... Why not using a plane dumb window?

Bad rendering - texts are jumping back from the next side just to be not really there, where one can see them. You have to scroll up and down to make word redraw the entire area correctly. Clicking on the scrollbar doesn&#039;t bring you to the corresponding area in the document, though the scrollbar grabber(how is this thing called?) gets moved to that place. For you microsoft people who don&#039;t know that: there are two options in the system preferences! Clicking to the scrollbar can really mean to scroll to that place (like on windows) or really jumpt there!

And why the hell is there no VBA? Is it that hard? This is one of THE BIG REASONS to use MS office.

As I first used the I was totally shocked. How can such a big and powerful company like MS bring such crap to the market? Did anybody test this? Then the first updates came out (promising perfomance improvements, etc ...) and I couldn&#039;t install them, because the installer didn&#039;t find my MS installation ... Such things MUST NOT HAPPEN! Shame on you, really!

If openoffice wouldn&#039;t bad so bad I&#039;d use it. But unfortunately it&#039;s slow, has bad rendering, bad usability. So why do I still use office 2008? Because I need to have compatibility to windows office 2003/2007. That&#039;s the only reason ...</description>
		<content:encoded><![CDATA[<p>The spaces/toolbar problem could be solved so easily. I guess there is some kind of event that is raised before/when the space changes. Just hde the toolbar or make word inactive (eg. focus finder) and it won&#8217;t get moved to the next space. If you use cmd-tab to jump to another application on a different space, the toolbar doesn&#8217;t get moved because the app is activated, word is deactivated and the toolbar is hidden &#8230;</p>
<p>What was said about performance has nothing to do with 30000 pixels or what so ever. Sometimes I feel like being near a singularity because word is so slow. Add a picture and then wait a few seconds before it is drawn. There a plenty of other situation, where the speed just sucks. And my documents are not even big. Just admit it, the codebase is a mess. The implementation is just bad! Making such an ugly hacked toolbar &#8230; Why not using a plane dumb window?</p>
<p>Bad rendering &#8211; texts are jumping back from the next side just to be not really there, where one can see them. You have to scroll up and down to make word redraw the entire area correctly. Clicking on the scrollbar doesn&#8217;t bring you to the corresponding area in the document, though the scrollbar grabber(how is this thing called?) gets moved to that place. For you microsoft people who don&#8217;t know that: there are two options in the system preferences! Clicking to the scrollbar can really mean to scroll to that place (like on windows) or really jumpt there!</p>
<p>And why the hell is there no VBA? Is it that hard? This is one of THE BIG REASONS to use MS office.</p>
<p>As I first used the I was totally shocked. How can such a big and powerful company like MS bring such crap to the market? Did anybody test this? Then the first updates came out (promising perfomance improvements, etc &#8230;) and I couldn&#8217;t install them, because the installer didn&#8217;t find my MS installation &#8230; Such things MUST NOT HAPPEN! Shame on you, really!</p>
<p>If openoffice wouldn&#8217;t bad so bad I&#8217;d use it. But unfortunately it&#8217;s slow, has bad rendering, bad usability. So why do I still use office 2008? Because I need to have compatibility to windows office 2003/2007. That&#8217;s the only reason &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Risks and Rewards by Steven</title>
		<link>http://www.schwieb.com/blog/2008/10/23/risks-and-rewards/comment-page-1/#comment-35908</link>
		<dc:creator>Steven</dc:creator>
		<pubDate>Wed, 10 Jun 2009 03:06:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=112#comment-35908</guid>
		<description>Schwieb, your post is all well and good. But why not just tell the blunt truth to everyone; 1) PowerPlant is in use all over Office, and 2) such code was NEVER supposed to make it to Intel.

Your team had plenty of time to re-implement plenty of Office over to Cocoa, and at least pure Carbon. I can&#039;t even begin to imagine what kind of job it was to wrap PowerPlant inside Carbon so it would compile on Intel. Sadly, such a feat is extremely impressive (and extremely time-wasting). Software Engineering 101 tells us that if we need to spend 8 months porting someone else&#039;s (Metrowerks) product so we don&#039;t have to rewrite ours, YOU&#039;RE DOING IT WRONG! 

So instead of doing the responsible thing and creating a decent product, Office sucks, and people are finally starting to give it up in favor of OpenOffice and iWork.

Way to go MS!</description>
		<content:encoded><![CDATA[<p>Schwieb, your post is all well and good. But why not just tell the blunt truth to everyone; 1) PowerPlant is in use all over Office, and 2) such code was NEVER supposed to make it to Intel.</p>
<p>Your team had plenty of time to re-implement plenty of Office over to Cocoa, and at least pure Carbon. I can&#8217;t even begin to imagine what kind of job it was to wrap PowerPlant inside Carbon so it would compile on Intel. Sadly, such a feat is extremely impressive (and extremely time-wasting). Software Engineering 101 tells us that if we need to spend 8 months porting someone else&#8217;s (Metrowerks) product so we don&#8217;t have to rewrite ours, YOU&#8217;RE DOING IT WRONG! </p>
<p>So instead of doing the responsible thing and creating a decent product, Office sucks, and people are finally starting to give it up in favor of OpenOffice and iWork.</p>
<p>Way to go MS!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Saying hello (again) to Visual Basic by Stuke</title>
		<link>http://www.schwieb.com/blog/2008/05/13/saying-hello-again-to-visual-basic/comment-page-3/#comment-35907</link>
		<dc:creator>Stuke</dc:creator>
		<pubDate>Tue, 09 Jun 2009 02:45:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35907</guid>
		<description>Well, a little over a year since my last post, and Microsoft is still &quot;confident&quot; they&#039;re making the right decision and timing to bring VBA back to Office.  Great, I get to pay $100s to upgrade to Office for the Mac 2011/2012 and get the functionality of 2004, maybe something more.  Are you kidding?

By 2011/2012, Apple&#039;s Numbers will mature, OO/NeoOffice will have grown on more desktops, and Microsoft will (re-)introduce VB in Office.  Don&#039;t you guys see a problem here?  You&#039;ll on the downward slide as a result of 2008.  Yes, as Apple&#039;s market share rises and moms and dads equip those school machines with Office (&quot;because we need it&quot;), you&#039;ll continue to have the &quot;cool-boss-guy&quot; tell the world 2008 sales are phenomena.  But, your customer base will actually shrink as those new Mac users file other means of producting &quot;office&quot; documents on the Mac.

Here&#039;s the only way to redeem yourself in 2011/2012.  Have all those Product IDs of paid 2008 customers entire them to a completely free version of 2011/2012.  Then we&#039;ll see how sincere the Mac BU/Microsoft is about it&#039;s Mac base.  You&#039;ll definitely re-ignite some level of true loyalty from the Mac community.  Charge $129 or $349 for an upgrade and it will be Adios for good!</description>
		<content:encoded><![CDATA[<p>Well, a little over a year since my last post, and Microsoft is still &#8220;confident&#8221; they&#8217;re making the right decision and timing to bring VBA back to Office.  Great, I get to pay $100s to upgrade to Office for the Mac 2011/2012 and get the functionality of 2004, maybe something more.  Are you kidding?</p>
<p>By 2011/2012, Apple&#8217;s Numbers will mature, OO/NeoOffice will have grown on more desktops, and Microsoft will (re-)introduce VB in Office.  Don&#8217;t you guys see a problem here?  You&#8217;ll on the downward slide as a result of 2008.  Yes, as Apple&#8217;s market share rises and moms and dads equip those school machines with Office (&#8220;because we need it&#8221;), you&#8217;ll continue to have the &#8220;cool-boss-guy&#8221; tell the world 2008 sales are phenomena.  But, your customer base will actually shrink as those new Mac users file other means of producting &#8220;office&#8221; documents on the Mac.</p>
<p>Here&#8217;s the only way to redeem yourself in 2011/2012.  Have all those Product IDs of paid 2008 customers entire them to a completely free version of 2011/2012.  Then we&#8217;ll see how sincere the Mac BU/Microsoft is about it&#8217;s Mac base.  You&#8217;ll definitely re-ignite some level of true loyalty from the Mac community.  Charge $129 or $349 for an upgrade and it will be Adios for good!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
