<?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: Saying hello (again) to Visual Basic</title>
	<atom:link href="http://www.schwieb.com/blog/2008/05/13/saying-hello-again-to-visual-basic/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic</link>
	<description>Random blatherings</description>
	<lastBuildDate>Thu, 11 Mar 2010 20:50:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Clifford Longley</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+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>By: Anonymous</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+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>By: Thomas Roll</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+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>By: John</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+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>By: Phillip Blue</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+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>By: Oakland Tracy</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+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>By: Chris</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+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>By: Stuke</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+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>
	<item>
		<title>By: Mark Eisler</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35906</link>
		<dc:creator>Mark Eisler</dc:creator>
		<pubDate>Mon, 08 Jun 2009 19:58:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35906</guid>
		<description>I have just switched to Mac from Windows as much for the quality of the hardware (Macbook Pro 15&quot; with SSHD) as the elegant OS, with both of which I am entirely delighted.  Like other commentators before me, I was not forewarned of the unexpected lack of VB in the current version of Office for Mac (2008).  It is a complete and utter disappointment and deal breaker!

Over the years I have built up a library of custom Excel functions and write and use a number of VB programs having Excel as the user interface in research and teaching in veterinary science.   Without these, Excel seems rather toothless and holds little thrall for me.  Indeed I might as well use a free spreadsheet such as the online Google Documents for simpler spreadsheet tasks.  To have to run Windows on my Mac and / or load an earlier version of Office for Mac seems such a retrograde step!  A free upgrade to the next version of Office for Mac with VB support for those of us who have unwisely invested in v2008 would be the very least we should expect!  I&#039;m not saying anything new here, mainly just adding another name to the petition to MacBU to keep its promise!</description>
		<content:encoded><![CDATA[<p>I have just switched to Mac from Windows as much for the quality of the hardware (Macbook Pro 15&#8243; with SSHD) as the elegant OS, with both of which I am entirely delighted.  Like other commentators before me, I was not forewarned of the unexpected lack of VB in the current version of Office for Mac (2008).  It is a complete and utter disappointment and deal breaker!</p>
<p>Over the years I have built up a library of custom Excel functions and write and use a number of VB programs having Excel as the user interface in research and teaching in veterinary science.   Without these, Excel seems rather toothless and holds little thrall for me.  Indeed I might as well use a free spreadsheet such as the online Google Documents for simpler spreadsheet tasks.  To have to run Windows on my Mac and / or load an earlier version of Office for Mac seems such a retrograde step!  A free upgrade to the next version of Office for Mac with VB support for those of us who have unwisely invested in v2008 would be the very least we should expect!  I&#8217;m not saying anything new here, mainly just adding another name to the petition to MacBU to keep its promise!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Toby</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35904</link>
		<dc:creator>Toby</dc:creator>
		<pubDate>Sat, 30 May 2009 22:47:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35904</guid>
		<description>When exactly is the VB version going to be available, and can we patch it in to the Office 2008 for Mac?

(I, too, am very disappointed about the totally unexpected lack of Macro editing capacity in the new version. I have created 33 macros for use in my professional translating work, and must use an older version of Word to operate them.)</description>
		<content:encoded><![CDATA[<p>When exactly is the VB version going to be available, and can we patch it in to the Office 2008 for Mac?</p>
<p>(I, too, am very disappointed about the totally unexpected lack of Macro editing capacity in the new version. I have created 33 macros for use in my professional translating work, and must use an older version of Word to operate them.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SectVGym</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35892</link>
		<dc:creator>SectVGym</dc:creator>
		<pubDate>Mon, 27 Apr 2009 13:55:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35892</guid>
		<description>I need VB now, not later.  I need it for the scorekeeping program and the state qualifying program that was written for our gymnastics program.  I didn&#039;t know our program used VB until I tried to open our scorekeeping program to check some scores and I got the &quot;Visual Basics does not work in Office 2008 for Mac&quot; message...I want to throw up.  It eliminated errors in choosing qualified participants to advance to state competition.  I don&#039;t know much about this programming stuff, but I want to be able to open a program and have it work.  Period, end of sentence.

I am a simple end user.  I don&#039;t know what else to do besides uninstall Office 2008 and put it in the shredder.  Thanks for making me miserable.</description>
		<content:encoded><![CDATA[<p>I need VB now, not later.  I need it for the scorekeeping program and the state qualifying program that was written for our gymnastics program.  I didn&#8217;t know our program used VB until I tried to open our scorekeeping program to check some scores and I got the &#8220;Visual Basics does not work in Office 2008 for Mac&#8221; message&#8230;I want to throw up.  It eliminated errors in choosing qualified participants to advance to state competition.  I don&#8217;t know much about this programming stuff, but I want to be able to open a program and have it work.  Period, end of sentence.</p>
<p>I am a simple end user.  I don&#8217;t know what else to do besides uninstall Office 2008 and put it in the shredder.  Thanks for making me miserable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35891</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sat, 25 Apr 2009 13:23:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35891</guid>
		<description>This is a bummer no doubt.  The main problem, there IS NO INDICATION ANYWHERE OF THIS HUGE ISSUE AT TIME OF PURCHASE!!! I was repeatedly told by ads and sales people for Mac that my files would be compatible.  I don&#039;t own an earlier version, so cannot solve my problem that way...if that&#039;s what I need to make this run as promised I should NOT have to purchase it.  I bought my Mac and the Office suite just a few months ago.  Now I find I am stopped in my tracks.  Of course, I have not been able to find an older version to download IF I was willing to pay the extortion fee.  JW</description>
		<content:encoded><![CDATA[<p>This is a bummer no doubt.  The main problem, there IS NO INDICATION ANYWHERE OF THIS HUGE ISSUE AT TIME OF PURCHASE!!! I was repeatedly told by ads and sales people for Mac that my files would be compatible.  I don&#8217;t own an earlier version, so cannot solve my problem that way&#8230;if that&#8217;s what I need to make this run as promised I should NOT have to purchase it.  I bought my Mac and the Office suite just a few months ago.  Now I find I am stopped in my tracks.  Of course, I have not been able to find an older version to download IF I was willing to pay the extortion fee.  JW</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35875</link>
		<dc:creator>Nathan</dc:creator>
		<pubDate>Sat, 28 Mar 2009 14:08:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35875</guid>
		<description>In  my view, Microsoft has revealed either its incompetence and/or its desire to punish apple.  I suspect some combination of both. I am amazed that the business community continues to rely on such an unstable and unreliable product.</description>
		<content:encoded><![CDATA[<p>In  my view, Microsoft has revealed either its incompetence and/or its desire to punish apple.  I suspect some combination of both. I am amazed that the business community continues to rely on such an unstable and unreliable product.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yves Champollion</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35863</link>
		<dc:creator>Yves Champollion</dc:creator>
		<pubDate>Mon, 16 Mar 2009 23:01:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35863</guid>
		<description>I code the Wordfast translation tool used by dozens of thousands of translators, Mac users included.

The removal of VBA in Office 2008/Mac is primarily a problem for... Ms-Office. What I mean is that translators who buy a Mac and/or Office do it thinking &quot;will that run Wordfast?&quot;. So they stick to Word:2004. That&#039;s what they all tell me. They&#039;ll skip Office 2008, it&#039;s that simple. Just fine. 2004 is stable, 2008 doesn&#039;t offer any cutting edge anyway. As far as Mac-based translators are concerned, MS will not recoup its investment in Office 2008, but we&#039;re unhurt - there seems to be a justice out there.

MS seems to be now run on short-term ROI principles. In the Bill Gates era, parting with VB was an unthinkable thing. A Word processor (Word) is a processor, a number cruncher (Excel) is a cruncher, at least he got that right. An application that can neither process nor crunch on automatic is a crippled one. Let&#039;s hope the recession restores vision and reason at the helm.</description>
		<content:encoded><![CDATA[<p>I code the Wordfast translation tool used by dozens of thousands of translators, Mac users included.</p>
<p>The removal of VBA in Office 2008/Mac is primarily a problem for&#8230; Ms-Office. What I mean is that translators who buy a Mac and/or Office do it thinking &#8220;will that run Wordfast?&#8221;. So they stick to Word:2004. That&#8217;s what they all tell me. They&#8217;ll skip Office 2008, it&#8217;s that simple. Just fine. 2004 is stable, 2008 doesn&#8217;t offer any cutting edge anyway. As far as Mac-based translators are concerned, MS will not recoup its investment in Office 2008, but we&#8217;re unhurt &#8211; there seems to be a justice out there.</p>
<p>MS seems to be now run on short-term ROI principles. In the Bill Gates era, parting with VB was an unthinkable thing. A Word processor (Word) is a processor, a number cruncher (Excel) is a cruncher, at least he got that right. An application that can neither process nor crunch on automatic is a crippled one. Let&#8217;s hope the recession restores vision and reason at the helm.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35859</link>
		<dc:creator>Anthony</dc:creator>
		<pubDate>Thu, 05 Mar 2009 07:36:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35859</guid>
		<description>Up until excel 2008 I was happy to fork out my hard earns for mac office. I felt I was getting value for my business. I use VBA extensively and this new version does not do half of what excel 2004 did for me.  2004 was good but awfully slow compared to excel 2007 for windows so I decided to bite the bullet and buy Office 2007 which I have to boot up in bootcamp. Excel 2007 is great, but that is the best I can say for windows other programs (that I have tried) and OS. I want mac excel to be at the very least, comparable to excel 2007 for windows and I want it now so I will not have to use windows at all.</description>
		<content:encoded><![CDATA[<p>Up until excel 2008 I was happy to fork out my hard earns for mac office. I felt I was getting value for my business. I use VBA extensively and this new version does not do half of what excel 2004 did for me.  2004 was good but awfully slow compared to excel 2007 for windows so I decided to bite the bullet and buy Office 2007 which I have to boot up in bootcamp. Excel 2007 is great, but that is the best I can say for windows other programs (that I have tried) and OS. I want mac excel to be at the very least, comparable to excel 2007 for windows and I want it now so I will not have to use windows at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Claire</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35857</link>
		<dc:creator>Claire</dc:creator>
		<pubDate>Tue, 10 Feb 2009 18:20:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35857</guid>
		<description>Is there any deadline for when the new office with Excel VBA will be available? Just figures today that my office 2008 doesn&#039;t support this... Is there no download available so VBA can be used in the meantime?</description>
		<content:encoded><![CDATA[<p>Is there any deadline for when the new office with Excel VBA will be available? Just figures today that my office 2008 doesn&#8217;t support this&#8230; Is there no download available so VBA can be used in the meantime?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guy Gallo</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35854</link>
		<dc:creator>Guy Gallo</dc:creator>
		<pubDate>Thu, 29 Jan 2009 16:16:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35854</guid>
		<description>As a developer for Word since version 2.0 on Windows, it&#039;s a little odd to phrase the question &quot;what parts of VBA are important...&quot;

The entire design of this word processor and what made it so interesting to program for -- is that anything you can do in the application UI was accessible through wordBasic (and then VBA).  That one to one correspondence has diminished over time -- but should still be a goal.

The IDE in MacVBA has never been on a par with the Windows IDE.  AutoComplete and keystroke access to parameters (for instance).  The link between IDE and Help items more tightly integrated.  It would be nice to have them a bit more on par.

A cross platform nightmare has always been how dialogs (due to differences in font rendering) do not translate.  What looks great on the Mac is too big on the PC, what&#039;s right for the PC is illegible on the mac.  The only workaround is to customize every dialog with a custom (and more mappable font) -- like Courier.  It would be great if there was some sort of translation table/conversion.

Importing forms/modules did not work on the mac as it does on the PC -- which makes module management and cleaning of templates harder.

Other than that -- anything the PC can do the Mac VBA should be able to do the same.  The exceptions really are limited to OLE integration and Shell(api) commands which need to be reprogrammed using AppleScript on the mac.  (examples of how to do that would be nice).</description>
		<content:encoded><![CDATA[<p>As a developer for Word since version 2.0 on Windows, it&#8217;s a little odd to phrase the question &#8220;what parts of VBA are important&#8230;&#8221;</p>
<p>The entire design of this word processor and what made it so interesting to program for &#8212; is that anything you can do in the application UI was accessible through wordBasic (and then VBA).  That one to one correspondence has diminished over time &#8212; but should still be a goal.</p>
<p>The IDE in MacVBA has never been on a par with the Windows IDE.  AutoComplete and keystroke access to parameters (for instance).  The link between IDE and Help items more tightly integrated.  It would be nice to have them a bit more on par.</p>
<p>A cross platform nightmare has always been how dialogs (due to differences in font rendering) do not translate.  What looks great on the Mac is too big on the PC, what&#8217;s right for the PC is illegible on the mac.  The only workaround is to customize every dialog with a custom (and more mappable font) &#8212; like Courier.  It would be great if there was some sort of translation table/conversion.</p>
<p>Importing forms/modules did not work on the mac as it does on the PC &#8212; which makes module management and cleaning of templates harder.</p>
<p>Other than that &#8212; anything the PC can do the Mac VBA should be able to do the same.  The exceptions really are limited to OLE integration and Shell(api) commands which need to be reprogrammed using AppleScript on the mac.  (examples of how to do that would be nice).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dan</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35853</link>
		<dc:creator>dan</dc:creator>
		<pubDate>Thu, 22 Jan 2009 01:32:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35853</guid>
		<description>i just bought Office 08 without any knowledge of the lack of VBA support for the software and i am very much not happy about it.  But if you are bringing VBA back in the next version of Office it would make me much happier.

As far as what i would like to see for VBA in the next Office...  i don&#039;t think you should change the look and feel of the developement environment too much, i feel you may alienate a large base of VBA users by changing where things are and how you go about finding them.  i feel much the same way for the object model, it would be kinda turn off to find objects don&#039;t work the same between MAC and Windows Office.  one thing i have always wanted in VBA i would be to have the ability to add fully functioning objects of own in VB world.  this may be a bit much to add, but for an old object oriented programmer like myself i would really like more OO characteristics in the VBA model.

until i get VBA support for mac i am forced to play my version of PONG in excel on windows.  why shouldn&#039;t i be able to play on mac?</description>
		<content:encoded><![CDATA[<p>i just bought Office 08 without any knowledge of the lack of VBA support for the software and i am very much not happy about it.  But if you are bringing VBA back in the next version of Office it would make me much happier.</p>
<p>As far as what i would like to see for VBA in the next Office&#8230;  i don&#8217;t think you should change the look and feel of the developement environment too much, i feel you may alienate a large base of VBA users by changing where things are and how you go about finding them.  i feel much the same way for the object model, it would be kinda turn off to find objects don&#8217;t work the same between MAC and Windows Office.  one thing i have always wanted in VBA i would be to have the ability to add fully functioning objects of own in VB world.  this may be a bit much to add, but for an old object oriented programmer like myself i would really like more OO characteristics in the VBA model.</p>
<p>until i get VBA support for mac i am forced to play my version of PONG in excel on windows.  why shouldn&#8217;t i be able to play on mac?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VBA to return in the next version of Office Mac !? &#124; keyongtech</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35850</link>
		<dc:creator>VBA to return in the next version of Office Mac !? &#124; keyongtech</dc:creator>
		<pubDate>Sun, 18 Jan 2009 16:46:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35850</guid>
		<description>[...] VBA to return in the next version of Office Mac !?     More info here: http://www.schwieb.com/blog/2008/05/...-visual-basic/  Whether it&#039;s worth rewriting macros or not depends on you and what you need them for.  Note that [...]</description>
		<content:encoded><![CDATA[<p>[...] VBA to return in the next version of Office Mac !?     More info here: <a href="http://www.schwieb.com/blog/2008/05/...-visual-basic/" rel="nofollow">http://www.schwieb.com/blog/2008/05/&#8230;-visual-basic/</a>  Whether it&#8217;s worth rewriting macros or not depends on you and what you need them for.  Note that [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Stepanek</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35848</link>
		<dc:creator>Tony Stepanek</dc:creator>
		<pubDate>Sat, 17 Jan 2009 13:11:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35848</guid>
		<description>I&#039;ve created my personal Time Journaling System based on Outlook and VBA functionality.
Task records in special folders acts like projects and sub-tasks, special contact folder is used as a list of partners and special journal folder with my own template works for journaling of time used for particular project, task and partner.
Even in the journal template, there is VBA script for internal functionality. Most of the evaluation is than based on VBA macros with dialogs etc. and even reports are created from Outlooks VBA by connection to Word.

I plan to switch to Mac, but missing VBA is a kind of trouble. As a freelancer, but with several partners using my Time Journaling System as well I need it for daily use.

I do use VBA in Excel for simple data transformations or for simple program solvers.

Having VBA in Office:mac would be great.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve created my personal Time Journaling System based on Outlook and VBA functionality.<br />
Task records in special folders acts like projects and sub-tasks, special contact folder is used as a list of partners and special journal folder with my own template works for journaling of time used for particular project, task and partner.<br />
Even in the journal template, there is VBA script for internal functionality. Most of the evaluation is than based on VBA macros with dialogs etc. and even reports are created from Outlooks VBA by connection to Word.</p>
<p>I plan to switch to Mac, but missing VBA is a kind of trouble. As a freelancer, but with several partners using my Time Journaling System as well I need it for daily use.</p>
<p>I do use VBA in Excel for simple data transformations or for simple program solvers.</p>
<p>Having VBA in Office:mac would be great.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VBA and VSTA - The Future? - Shaun Cassells at MyITForum.com</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35641</link>
		<dc:creator>VBA and VSTA - The Future? - Shaun Cassells at MyITForum.com</dc:creator>
		<pubDate>Tue, 08 Jul 2008 18:42:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35641</guid>
		<description>[...] Does this mean the next version of office (2010) will no&#160;longer support VBA macros? &#160; &#160; &#160;&#160;&#160; Looking a little further, I discovered VBA support was removed from MAC&#160;Office 2008 because of the PPC to x86&#160;processor change.&#160; However, the lead programmer for windows says VBA will be returned to next office revision http://www.schwieb.com/blog/2008/05/13/saying-hello-again-to-visual-basic/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Does this mean the next version of office (2010) will no&nbsp;longer support VBA macros? &nbsp; &nbsp; &nbsp;&nbsp;&nbsp; Looking a little further, I discovered VBA support was removed from MAC&nbsp;Office 2008 because of the PPC to x86&nbsp;processor change.&nbsp; However, the lead programmer for windows says VBA will be returned to next office revision <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>By: L. Crowe</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35619</link>
		<dc:creator>L. Crowe</dc:creator>
		<pubDate>Fri, 04 Jul 2008 21:09:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35619</guid>
		<description>I write a lot of Macros via Word 2003 and Visual Basic on an XP machine, which are then used by numerous staff members multiple times a day. Worries about macros being potentially broken by changes in any given OS/Office upgrades (be it in Vista or Mac OSX) certainly slow down company&#039;s ability to bring in new machines and roll out new upgrades -- too much testing is needed first, too many little compatibility worries . . . Dropping Visual Basic from Mac Office 2008 just makes things worse. So I&#039;m glad to hear that VB will be coming back in the future -- I&#039;ll likely buy Mac Office at least for myself at that time. Until then, I&#039;ll stick with older versions of Office or will make sure to the Windows versions via Parallels on my Mac. . .  Many thanks for working on this!</description>
		<content:encoded><![CDATA[<p>I write a lot of Macros via Word 2003 and Visual Basic on an XP machine, which are then used by numerous staff members multiple times a day. Worries about macros being potentially broken by changes in any given OS/Office upgrades (be it in Vista or Mac OSX) certainly slow down company&#8217;s ability to bring in new machines and roll out new upgrades &#8212; too much testing is needed first, too many little compatibility worries . . . Dropping Visual Basic from Mac Office 2008 just makes things worse. So I&#8217;m glad to hear that VB will be coming back in the future &#8212; I&#8217;ll likely buy Mac Office at least for myself at that time. Until then, I&#8217;ll stick with older versions of Office or will make sure to the Windows versions via Parallels on my Mac. . .  Many thanks for working on this!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SP1 f&#252;r MS Office 2008 Mac erschienen at NETWAYS Blog</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35343</link>
		<dc:creator>SP1 f&#252;r MS Office 2008 Mac erschienen at NETWAYS Blog</dc:creator>
		<pubDate>Wed, 11 Jun 2008 21:02:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35343</guid>
		<description>[...] es in Office 2008 nachzur&#252;sten. Es gibt dazu eine offizielle Pressemeldung und einen Blogpost, der die Hintergr&#252;nde [...]</description>
		<content:encoded><![CDATA[<p>[...] es in Office 2008 nachzur&#252;sten. Es gibt dazu eine offizielle Pressemeldung und einen Blogpost, der die Hintergr&#252;nde [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Back to Basic (Visual Basic) &#124; alexmak.net</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35112</link>
		<dc:creator>Back to Basic (Visual Basic) &#124; alexmak.net</dc:creator>
		<pubDate>Mon, 26 May 2008 06:03:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35112</guid>
		<description>[...] ????? ?? ??????? Office ??? ????????? ???. ? ?????????, ???????????? ????????, ??? ????????? Visual Basic ???????? ? ???? ?? ????????? [...]</description>
		<content:encoded><![CDATA[<p>[...] ????? ?? ??????? Office ??? ????????? ???. ? ?????????, ???????????? ????????, ??? ????????? Visual Basic ???????? ? ???? ?? ????????? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: currie</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35057</link>
		<dc:creator>currie</dc:creator>
		<pubDate>Wed, 21 May 2008 12:24:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35057</guid>
		<description>I have VMWare Fusion, and can run Windows XP with applications on it for work (particularly Framemaker, Netmeeting, Windows specific tools like VoIP phones, and Office). My company is big on using Word/Excel/Powerpoint.

However, I have found that NeoOffice is quite capable of opening Word/Excel/Powerpoint files and resaving them as Office documents. I have a 2GHz 2GB ram Macbook Duo_core.

The Neooffice site states at http://www.neooffice.org/neojava/en/features.php

Handles Most Excel VBA Macros	NeoOffice includes the Excel macro support developed by Novell&#039;s ooo-build project. The ooo-build project is an open source project that continually develops feature enhancements to OpenOffice.org.

And its free too. I urge you to download it with the latest patches and try it. Set its preferences to save as Office format instead of its own format.</description>
		<content:encoded><![CDATA[<p>I have VMWare Fusion, and can run Windows XP with applications on it for work (particularly Framemaker, Netmeeting, Windows specific tools like VoIP phones, and Office). My company is big on using Word/Excel/Powerpoint.</p>
<p>However, I have found that NeoOffice is quite capable of opening Word/Excel/Powerpoint files and resaving them as Office documents. I have a 2GHz 2GB ram Macbook Duo_core.</p>
<p>The Neooffice site states at <a href="http://www.neooffice.org/neojava/en/features.php" rel="nofollow">http://www.neooffice.org/neojava/en/features.php</a></p>
<p>Handles Most Excel VBA Macros	NeoOffice includes the Excel macro support developed by Novell&#8217;s ooo-build project. The ooo-build project is an open source project that continually develops feature enhancements to OpenOffice.org.</p>
<p>And its free too. I urge you to download it with the latest patches and try it. Set its preferences to save as Office format instead of its own format.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35051</link>
		<dc:creator>Ed</dc:creator>
		<pubDate>Wed, 21 May 2008 03:48:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35051</guid>
		<description>You have commented that despite the short falls of Office 2008, it is selling well.  In my case, I purchased it prior to realizing it had been neutered. I welcome VB&#039;s return, I used to use it constantly.  By the way, I am now a two computer user, my old lap top sits at the side of my new one just so I can run what I need to.  Please double your efforts to restore to faithful long term users the tools we trusted would always be available.  Dumbing down a product is never a way to win up grading customers, failing to publicize adequately the neutering of excel prior to its release left me an extremely disillusioned user.  My mouth dropped when I realized I had just spent money on a giant step backwards.  So thank you for for working on bringing it back.  Will it be a software update, or a repurchase?</description>
		<content:encoded><![CDATA[<p>You have commented that despite the short falls of Office 2008, it is selling well.  In my case, I purchased it prior to realizing it had been neutered. I welcome VB&#8217;s return, I used to use it constantly.  By the way, I am now a two computer user, my old lap top sits at the side of my new one just so I can run what I need to.  Please double your efforts to restore to faithful long term users the tools we trusted would always be available.  Dumbing down a product is never a way to win up grading customers, failing to publicize adequately the neutering of excel prior to its release left me an extremely disillusioned user.  My mouth dropped when I realized I had just spent money on a giant step backwards.  So thank you for for working on bringing it back.  Will it be a software update, or a repurchase?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Norton</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35044</link>
		<dc:creator>Doug Norton</dc:creator>
		<pubDate>Tue, 20 May 2008 17:15:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35044</guid>
		<description>We call DLL&#039;s on the PC and shared libraries on the Mac.  Please include declares of frameworks on  in VBA for Mac.  Object parity with PC word objects is also very important.

Anyway to be in on an early release?  We&#039;ll sign an NDA...  Thanks! -doug</description>
		<content:encoded><![CDATA[<p>We call DLL&#8217;s on the PC and shared libraries on the Mac.  Please include declares of frameworks on  in VBA for Mac.  Object parity with PC word objects is also very important.</p>
<p>Anyway to be in on an early release?  We&#8217;ll sign an NDA&#8230;  Thanks! -doug</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carlos Le Mare</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35043</link>
		<dc:creator>Carlos Le Mare</dc:creator>
		<pubDate>Tue, 20 May 2008 17:05:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35043</guid>
		<description>More than VBA I miss a couple of programs to made Mac Platform a real deal for the enterprise:

1. Visio: There is a very good alternatives in Mac, but they are not binary compatibles with Visio. If port visio is too complicated or expensive, at least consider to create a convertion tool form the binary form to the xml form that run on Mac OS (Universal please)
2. Project: There are good alternatives to Project, but nothing that integrates with Project Server. Even you have a very good compatibility with the binary files, but if you work with Project Server... sorry, no macs allowed. (The web interface requires Internet Explorer, probably because of some activeX controls). At least consider create a web interface wich runs with safari and Firefox....

thanks.

clemare</description>
		<content:encoded><![CDATA[<p>More than VBA I miss a couple of programs to made Mac Platform a real deal for the enterprise:</p>
<p>1. Visio: There is a very good alternatives in Mac, but they are not binary compatibles with Visio. If port visio is too complicated or expensive, at least consider to create a convertion tool form the binary form to the xml form that run on Mac OS (Universal please)<br />
2. Project: There are good alternatives to Project, but nothing that integrates with Project Server. Even you have a very good compatibility with the binary files, but if you work with Project Server&#8230; sorry, no macs allowed. (The web interface requires Internet Explorer, probably because of some activeX controls). At least consider create a web interface wich runs with safari and Firefox&#8230;.</p>
<p>thanks.</p>
<p>clemare</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryce Glover</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35041</link>
		<dc:creator>Bryce Glover</dc:creator>
		<pubDate>Tue, 20 May 2008 14:59:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35041</guid>
		<description>I am only thirteen, yet even I use VBA scripting!  I use it to create a new journal entry by virtually hitting return, inserting a date that won&#039;t change, and hitting return again.  I execute this script by hitting the keystroke Option-F7.  It comes in handy.  I don&#039;t want to have to have to use Automator&#039;s Watch Me Do function to replicate VBA the VBA script macro recording function in Office 2008 for Mac.  So, if you could publish an update to Office &#039;08 as soon as you finish porting VBA scripting to Xcode, that would be great.  It would also be nice if you could make it so that the the little bar under the toolbar woul slide under the toolbar when not in use.  Then, when you mouse over to the toolbar, it would slide out.  It would act kind of like the Dock and the menu bar do when you are in Quick Look&#039;sfull screen mode.  Plus, you could make it a normal toolbar.  Everything counts for user-friendliness.  Thanks.</description>
		<content:encoded><![CDATA[<p>I am only thirteen, yet even I use VBA scripting!  I use it to create a new journal entry by virtually hitting return, inserting a date that won&#8217;t change, and hitting return again.  I execute this script by hitting the keystroke Option-F7.  It comes in handy.  I don&#8217;t want to have to have to use Automator&#8217;s Watch Me Do function to replicate VBA the VBA script macro recording function in Office 2008 for Mac.  So, if you could publish an update to Office &#8216;08 as soon as you finish porting VBA scripting to Xcode, that would be great.  It would also be nice if you could make it so that the the little bar under the toolbar woul slide under the toolbar when not in use.  Then, when you mouse over to the toolbar, it would slide out.  It would act kind of like the Dock and the menu bar do when you are in Quick Look&#8217;sfull screen mode.  Plus, you could make it a normal toolbar.  Everything counts for user-friendliness.  Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuke</title>
		<link>http://www.schwieb.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fwww.schwieb.com%2Fblog%2F2008%2F05%2F13%2Fsaying-hello-again-to-visual-basic%2F&amp;seed_title=Saying+hello+%28again%29+to+Visual+Basic/comment-page-3/#comment-35017</link>
		<dc:creator>Stuke</dc:creator>
		<pubDate>Sun, 18 May 2008 20:05:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwieb.com/blog/?p=70#comment-35017</guid>
		<description>VBA at the level it will be in the Windows version of Office at that time.

If we truly have to wait until 2010, 2011, or beyond, what have you been doing in Redmond?  Remember when Apple revealed that Mac OS X would run on Intel chip sets?  Three operating systems later, when they made the strategic announcement to switch from Motorola/IBM sets, they had ALREADY wrote Mac OS X to work on the Intel set.  Now how come the MacBU of Microsoft couldn&#039;t have thought the same way.  Oh, yeah, you&#039;re Microsoft not Apple.  But really, you mean to tell everyone that VBA will still be years away?  Honestly?  You don&#039;t have a group of programmers locked-up in a hole and are ready to release it with Office 2008 SP2???  It must be incredibly awkward to show up to work every day and feel like you&#039;re making a contribution to the world of computing!

Sorry for the harshness but after being treated like black americans (in the computer OS sense) for so long, you must understand.  We Mac users wouldn&#039;t feel this way if you didn&#039;t jerk us around.  We&#039;d be happy to use Office if it behaved just like it does on Windows so we can use the product at work AS WELL AS AT HOME AND SCHOOL.  Face it, Apple&#039;s Mac OS is not going away so you had better figure this out.

Oh, and your triple shipping numbers relative to Office 2004...guess which operation system continues to grow at about the same rate over the 2004 - 2008 time frame.  So, stoke-up the monkeys in the basement and finish the VBA programming for Office 2008 SP2 to have even a chance of being in the game come 2010, 2011, or beyond.</description>
		<content:encoded><![CDATA[<p>VBA at the level it will be in the Windows version of Office at that time.</p>
<p>If we truly have to wait until 2010, 2011, or beyond, what have you been doing in Redmond?  Remember when Apple revealed that Mac OS X would run on Intel chip sets?  Three operating systems later, when they made the strategic announcement to switch from Motorola/IBM sets, they had ALREADY wrote Mac OS X to work on the Intel set.  Now how come the MacBU of Microsoft couldn&#8217;t have thought the same way.  Oh, yeah, you&#8217;re Microsoft not Apple.  But really, you mean to tell everyone that VBA will still be years away?  Honestly?  You don&#8217;t have a group of programmers locked-up in a hole and are ready to release it with Office 2008 SP2???  It must be incredibly awkward to show up to work every day and feel like you&#8217;re making a contribution to the world of computing!</p>
<p>Sorry for the harshness but after being treated like black americans (in the computer OS sense) for so long, you must understand.  We Mac users wouldn&#8217;t feel this way if you didn&#8217;t jerk us around.  We&#8217;d be happy to use Office if it behaved just like it does on Windows so we can use the product at work AS WELL AS AT HOME AND SCHOOL.  Face it, Apple&#8217;s Mac OS is not going away so you had better figure this out.</p>
<p>Oh, and your triple shipping numbers relative to Office 2004&#8230;guess which operation system continues to grow at about the same rate over the 2004 &#8211; 2008 time frame.  So, stoke-up the monkeys in the basement and finish the VBA programming for Office 2008 SP2 to have even a chance of being in the game come 2010, 2011, or beyond.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
