Mac Office 2008 Development- AppleScript vs. VBA - vba

I'm looking for some advice from anyone who has experience writing addons for PowerPoint on both Windows and Mac machines.
We have a Windows Office 2007 addon (.NET) that we'd like to port to the Mac.
Thus, in PowerPoint 2008 for the Mac, we require the following functionality:
Ribbon/Fluent extensibility
Custom Task Panes
Read/write custom document properties
Save slides as images
Read text and shape information from slides
Get notification of the following PowerPoint application events; `SlideSelectionChanged`, `PresentationClose` and `AfterPresentationOpen`.
I am hoping someone with experience writing Office addons for Windows and Mac, can advise.

This doesn't solve your problem if you need to specifically do this in 2008, but Office 2011 is coming and it brings back VBA. Spending the effort to convert your stuff to AppleScript might be a lot of work for little return where you could wait for Office 2011 which brings the Ribbon to Mac Office as well as VBA...
http://www.computerworld.com/s/article/9085678/Microsoft_will_bring_back_macros_to_Mac_Office_in_2011

Related

VBA & Excel across different platforms

In my workplace we have several different types of systems.
Surface Pro's running Office 2016
Surface Pro's running Office 2013
Thin Clients running Office 2010
Desktops for Accessibility users running Office 2010
I develop VBA solutions that have to work across all of the above, and run into trouble with only one scenario.
I use a Surface Pro with Office 2016. If I build a document, I can run the macros I create on the Surface Pro's and Thin clients without issue, but the Desktop PC's running Office 2010 don't even get the option to turn on the macros.
If I open the file up on a desktop (seldom have access to one) and save it using that system, any other user on a desktop can open it up and the macros will work, but if anyone from one of the other systems opens it up and saves it, the desktop users will go back to square one.
At first I thought this would have been a compatibility issue relating to architecture
Can anyone think of anything before I pull the remainder of my hair out? I really want to be able to solve issues for the people having problems on desktops without having to find one myself, or worse - give them any passwords
Cheers
Go to VBA Tools and uncheck all objects marked as missing under References.

Run VBA on smartphone

I have searched high and low and I cant find if it is possible to run VBA on Samsung galaxy 5 using Excel 365 (Latest Version)
Was wondering if I take a subscription with 365 will it allow me to use vba
Thanks
#James: Specifically for Android, there is no application which allows you to run VBA, but e-Droid-Cell Pro Spreadsheet which includes a "Macro" mechanism allowing to script the application. Although the Macro language is not compatible with VBA (Visual Basic Applications) it does allows for doing almost anything required by a Macro language. Here is the Link of application on Google play store.
They have some really good reviews but I will suggest to try out the trial version first.
As for O365, If you have done any VBA development which works with Office 2010 or Office 2013 then it will work in Office 365, while you can open the book in the browser or through a webpage, you won't be able to run any of the vba code there.
the only solution i found was to install "OpenOffice" on my pc and opening my excel project with vba with OpenOffice, the vba of OpenOffice is near of exel vba you will need to convert somme instruction you will be able to convert, débugging and testing on your pc be sure to save as OpenOffice format. On your android tablet/phone install "AndrOpen Office" copy your new OpenOffice project to your tablet/phone and open it with AndrOpen Office. MAKE INTNESIF TEST

How to build native office for mac 2016 application (UI)

We build many office application for windows, and it work very natively with office UI but when we came to do same on office for mac we have been lost :(
We need an embedded native Microsoft word for MAC 2016 (better if works with Microsoft word for mac 2011 too)
*by native we mean to be embedded in word window, not like the VBA forms, like word panels etc
*The most important issue for us is the UI and how it will work like if it was built by Microsoft it self,
*ANY SOLUTION FOR MS-WORD FOR WINDOWS IS NOT WHAT WE ARE LOOKING FOR AT ALL, THE SCOPE IS MICROSOFT WORD BUT FOR MAC
*The UI we prefer first is something like word native pans such as
*Navigation pane
*Task pane
*Side bar/pan
if this not possible then 2nd option will be
*Ribbon
if this not possible then 3rd option will be
*Toolbox
We open to use any technology to build this, such as VBA,swift, objective-c whatever provide us with the solution we need,
Any advice??
As far as I am aware, the support for embedding native clients is going the way of the dodo. Everything is moving towards the Office Web Apps and embedding that view within applications. It might make sense to review if that allows for the functionality you are looking for based on how it's deployed.

Converting powerpoint VBA add-in (.ppam) to COM add-in (.dll)

I have created a working Powerpoint add-in (.ppam) that offers several time saving features, and added a custom UI ribbon tab to improve accessibility.
As I look to distribute this add-in to users, I'm looking to improve code security by compiling it into a COM add-in (.dll) via VS Express.
I have looked all over the web for documentation on this, and have found some promising source, such as:
http://www.cpearson.com/excel/creatingcomaddin.aspx
Unfortunately, nearly everything I find appear to be quite outdated and based on Office XP or 2003, when I'm looking at Office 2010. I'm probably doing something wrong here, but I'm having trouble replicating their instructions on my end, running into errors like being unable to add a reference library or the code they suggest is not recognized. I actually am even unsure how to open for example the sample VB project that the Pearson site provides from the link above to imitate. I think all this may be because of the different versions of Office and Visual Studio, but could certainly be wrong.
Could anyone point me in the right direction? My understanding is that it's actually quite simple to convert the code from VBA to VB (just involves adding "Powerpoint.Application." in front of things like "activewindow"). So I just need to figure out how to convert a very simple VBA add-in into a COM add-in in VS Exp 2012 for Office 2010, and then can leverage the process to convert the full add-in.
Apologies if I'm using any of the terms incorrectly.

Excel vba project in VB.NET

I am now engaging in an excel vba project. It's a excel front interface for the workers in a site with an Access database in the company network. I dont like much the VBE in Excel 2007, so im wandering if I can do this with VB.NET, which seems to be a more adorable IDE. And where can I find some resources on this? Or recommanded books? Thanks!
Im using Excel 2007 et VB.NET 2008
You could also try Excel-DNA (free). There are many other products out there too. You can make it work with VB.Net Express also, you just need to add a reference to your excel SDK. Also, Add-in Express looks pretty nice. I've never tried it though (costs money).
I think you are looking for Visual Studio Tools for Office: VSTO.
This allows you to develop using VB.NET (or indeed C#) but with full access to the Office automation facilities.