• Microsoft Word 16.0 Object Library
• Microsoft Powerpoint 16.0 Object Library
• Microsoft Office Object Library

Hello this is a follow up on this ticket:I developed a macro that exports something from excel to powerpoint in Excel 2010. I ran into issues when I tried to deploy to people with Office 2010. Per the advice of SO I changed the references to late binding to avoid version dependency. It is now possible to open and run the macro on office 2010 but users still see the error message: 'Trouble loading DLL'. It says missing 15 Powerpoint VBA when I click into the references.

If I uncheck this and check 14 it will run, but it seems like someone in 2010 will have to do this each time they run the Macro. Any advice on how to proceed?

I have written Visual Basic.NET application using Microsoft Excel 14.0 Object Library.I have Microsoft Office 2010 Installed on my machine, but my client using Microsoft Office 2007.Should I expect any difficulties installing the application on the client's machine, if so what should I do or be aware of?Or is there any way I could ad Microsoft Excel 2007 Object Library reference on my machine?Hi IgalWhich version of Visual Studio did you use? If it's VS 2010 then you can program against Office 2010 applications and your code can run in earlier versions - as long as you useonly features that are available in the earlier versions.By default, VS 2010 uses a new functionality that embeds the parts of thetype library you use into your.NET project. This makes the project version-independent and PIA-independent.If you use VS 2008 or earlier, this is not available to you. In that case, what Dennis said applies.I also feel it's important to correct the statement made in this discussion that the object library is part of a.exe file.

The Office object libraries are in.olb and.tlb files. But a.NET project does not work with these directly, as theseare COM. An 'translation interface' is required for a.NET app to be able to communicate with COM, as they use different data types and some other things are different. These 'translation interfaces' are called 'Interop Assemblies' (IAs) and can be generatedusing the tlbImp.exe tool that's part of Visual Studio. In this case, the IAs need to be distributed with the solution.

A software manufacturer can deliver an optimized set of IAs, called PIAs (Primary Interop Assembly). These are stored in the.NET GAC andare meant to be used by all developers and are what should be used in your Office projects.PIAs are version-dependent, but the Office 2007 and Office 2010 PIAs can recognize calls to Office 2003 PIAs and 're-route' these to themselves.

So it's possible to bring projects programmed against earlier versions of Office forward to newer versions, butnot vice-versa. If you want to program for multiple versions, you should therefore always program against theearlier version (and also because you can be sure that you aren't using any new features).Cindy Meister, VSTO/Word MVP. The microsoft excel 14.0 object library is an.EXE file. It is the excel program. I opened excel and look in the VBA menu Tools - References which gave me the name of the library.C:Program FilesMicrosoft OfficeOffice12Excel.exeI would think you would need to install Office 2007 on your machine to get the library. But then office 2010 is meant to work with Window 7 which are both 64 bit machines. Are they running window 7 on your clients PC?

Microsoft Word 16.0 Object Library

I don't think youwill be able to fully verify you application when you are running at one site a 64 bit environment and the 2nd site a 32 environment.jdweng. I have written Visual Basic.NET application using Microsoft Excel 14.0 Object Library.I have Microsoft Office 2010 Installed on my machine, but my client using Microsoft Office 2007.Should I expect any difficulties installing the application on the client's machine, if so what should I do or be aware of?Or is there any way I could ad Microsoft Excel 2007 Object Library reference on my machine?Hi IgalWhich version of Visual Studio did you use? If it's VS 2010 then you can program against Office 2010 applications and your code can run in earlier versions - as long as you useonly features that are available in the earlier versions.By default, VS 2010 uses a new functionality that embeds the parts of thetype library you use into your.NET project. This makes the project version-independent and PIA-independent.If you use VS 2008 or earlier, this is not available to you. In that case, what Dennis said applies.I also feel it's important to correct the statement made in this discussion that the object library is part of a.exe file. The Office object libraries are in.olb and.tlb files.

But a.NET project does not work with these directly, as theseare COM. An 'translation interface' is required for a.NET app to be able to communicate with COM, as they use different data types and some other things are different.

Microsoft Powerpoint 16.0 Object Library

Microsoft Office Object Library

Collectors edition 747 business stapler. These 'translation interfaces' are called 'Interop Assemblies' (IAs) and can be generatedusing the tlbImp.exe tool that's part of Visual Studio. In this case, the IAs need to be distributed with the solution. A software manufacturer can deliver an optimized set of IAs, called PIAs (Primary Interop Assembly). These are stored in the.NET GAC andare meant to be used by all developers and are what should be used in your Office projects.PIAs are version-dependent, but the Office 2007 and Office 2010 PIAs can recognize calls to Office 2003 PIAs and 're-route' these to themselves. So it's possible to bring projects programmed against earlier versions of Office forward to newer versions, butnot vice-versa. If you want to program for multiple versions, you should therefore always program against theearlier version (and also because you can be sure that you aren't using any new features).Cindy Meister, VSTO/Word MVP.