To answer a bunch of questions
zaphon said:
I just simply want to be able to open the majority of the documents I receive which have VBA macro's in them.
As we announced in May 2008, and have
consistently reaffirmed since them, VBA is returning to Office:Mac 2011. Specifically, we've brought VBA 6.5 to Office 2011.
costabunny said:
I will try the trial (if/when its released)
We had a trial for Office 2008, and we'll have a trial for Office 2011.
entropyfl said:
oh and one question for you beta testers on here. does the new mac outlook support public folders?
Well, I'm not a beta tester

, but yes, Outlook:Mac supports public folders in Exchange.
Kelmon said:
I'm also wondering what the obsession is with Web Services interfaces. Last I heard compatibility with Exchange and SharePoint required that both had Web Services enabled in order for the Mac applications to interact with them. I am 99% certain that they are not enabled on my company's servers which essentially means that the applications are not compatible. Moving to the future is nice but it doesn't seem to be helping in the present.
Outlook:Mac supports Exchange 2007 and Exchange 2010, both of which support (and have enabled by default) Exchange Web Services. If you're using Exchange 2003 or earlier, you'll need to continue using Entourage 2008 or earlier (or ask your Exchange admin to enable IMAP).
Our love of Exchange Web Services is twofold: it's way faster than the previous way to connect to Exchange (via WebDAV), and it provides lots more functionality to us. For example, with WebDAV, we couldn't support synchronisation of tasks, notes, and categories. Exchange Web Services totally changed that for us.
BayouMan said:
There isn't, and according to Microsoft never will be, a Mac version of Access.
I don't think we've ever said that there never would be Access on the Mac.
When we consider whether we should add another application to our portfolio, we have two major areas to consider:
1. What is the need? How many people need it? How are their needs being currently met (if at all)?
2. What is the cost? How much development effort will it require, how experienced do those developers need to be, and how long will it take them?
So far, the equation hasn't worked out in favour of bringing Access to the Mac. The cost of bringing Access to the Mac is high because it relies on many Windows OS features to function, and the need is relatively low. This is something we reevaluate frequently to determine if it's time to make a change.
MacRumorUser said:
I honestly believe Office for Mac 2011 development team deserve a pat on the back for the work they have done on it.
Thanks!
As we get closer to our launch in October, we'll be revealing more details about what's coming in Office 2011. There's several things that have been discussed in this thread that I want to comment on but can't yet -- suffice it to say that just because we haven't said anything about it yet doesn't mean that it's not happening in this release.
Regards,
Nadyne.