Re^4: Win32 OLE on Office 2013 64 bit

in reply to Re^3: Win32 OLE on Office 2013 64 bit
in thread Win32 OLE on Office 2013 64 bit

Use the OLEView tool AKA OLE/COM Object Viewer. Click on "Type Libraries" folder on the left and look for a relevant name. Another folder to try looking for names is Object Classes->All Objects. I'm not sure myself (or how to tell) what classes are constructable from scratch in OLEView and which ones can only be obtain through a reference returned from another class. Also, if you look at a class in OLEView (blue 3d square), and in the list of magnifying glasses, you will always see IUnknown, but if you don't see IDispatch in the same list as the IUnknown, that class is C++ only and not usable from Win32::OLE. You can also right click on the IDispatch, click View, then click View TypeInfo and get a list of method names and prototypes that you can call on that type.

Comment on Re^4: Win32 OLE on Office 2013 64 bit

Replies are listed 'Best First'.
Re^5: Win32 OLE on Office 2013 64 bit by mondokkia (Novice) on Dec 17, 2013 at 00:02 UTC
Thanks. I'll schedule a server downtime next week to try this out Will report out after that	[reply]
Re^6: Win32 OLE on Office 2013 64 bit by mondokkia (Novice) on Dec 23, 2013 at 02:18 UTC
So I ran OLEView and found a type library called "Microsoft Outlook 15.0 Object Library" and tried using that in the const declaration...strangely, no joy. I then exported the library info to .IDL file and compared that to Office 2010 IDL file, didn't see any difference that could cause this (just some class differences). I'm wondering if this could be a unregistered server or something? I'm at my wits end on this, I've been running this job manually and it's a real pain. Anyone have any other ideas I can try out?	[reply]

In Section Seekers of Perl Wisdom