I am currently coding a VB 6 DLL and a VB 6 EXE, each uses Excel 2003.

Both projects require the use of the Office 11 object library, which results
in a reference to the mso.d11 for Office 11, version 11.0.8221.0.

However, certain constants are not defined unless I include the MSO.dll for
what is called the Office 12 object library, version 12.0.6320.5000.

The file is Program Files\Common Files\Microsoft Shared\OFFICE12\mso.dll.
Office 2007 has never been on the computer being used.

Where did that file come from?
From an update to Office 2003?

Neither version is listed at http://support.microsoft.com/dllhelp/.

Hi Howard,

If the reference is set to the Office-11 mso.dll do *not* use any named
constants that are new in Office-12. Simply define your own say at module
level, you can use the same names, or use the intrinsic values.

Public Const msoThemeDark1 As Long = &H1

I can't imagine how \OFFICE12\mso.dll ever got onto the computer if Office
2007 has never been installed.

Regards,
Peter T

"Howard Kaikow" wrote in message
...
I am currently coding a VB 6 DLL and a VB 6 EXE, each uses Excel 2003.

Both projects require the use of the Office 11 object library, which
results
in a reference to the mso.d11 for Office 11, version 11.0.8221.0.

However, certain constants are not defined unless I include the MSO.dll
for
what is called the Office 12 object library, version 12.0.6320.5000.

The file is Program Files\Common Files\Microsoft Shared\OFFICE12\mso.dll.
Office 2007 has never been on the computer being used.

Where did that file come from?
From an update to Office 2003?

Neither version is listed at http://support.microsoft.com/dllhelp/.

I compiled 2 versions of the test program on my Office 2003 system.

In one, I used the Office12\mso.dsl. In the other, I used the
Office11\mso.dll.

I then copied the prohects for each to my Office 2007 system.

I opened each project on the Office 2003 system using VB 6. In both cases,
the Office 2007 Office12 mso.dll was substituted

I then compiled both projects using VB 6 in the Office 2007 system, and
moved them back to the Office 2003 system. They both ran.

I guess that MSFT's goal is to permit such back and forth, as long as you do
not use features present in Office 2007 that are not in the earlier versions
of interest. This makes sense.

But the puzzle remains as to why some folkes have the Office12 mso.dll and
others do not.

one possibility is that one might have to have a compiler, such as VB 6 or,
some other language, and not just office.

If you just write VBA code within Office, the Office12 mso.dll is not listed
as a reference.

However, if you compile with, say, VB 6, the Office 12 mso is listed, but
the Office 11 mso.dll is NOT listed, thou you can browse and brute force
reference the Office 11 version. I ASSuME that the Office 12 mso could also
be referenced from within VBA, but I would not try it.

But the puzzle remains as to why some folkes have the Office12 mso.dll and
others do not.

one possibility is that one might have to have a compiler, such as VB 6 or,
some other language, and not just office.

The Compatibility Pack may install the MSO.DLL version in question. Of
possibly one or another of the Office viewer apps (though not the PowerPoint
viewer ... I just checked that).

"Steve Rindsberg" wrote in message
...
But the puzzle remains as to why some folkes have the Office12 mso.dll
and
others do not.

one possibility is that one might have to have a compiler, such as VB 6
or,
some other language, and not just office.

The Compatibility Pack may install the MSO.DLL version in question. Of
possibly one or another of the Office viewer apps (though not the
PowerPoint
viewer ... I just checked that).

I do not have the Compatibility Pack, at least I never asked for it to be
installed, not do I have any viewer on ANY of thse systems with Office 2000,
XP, or 2003.

How could I determine whether I have the Compatibility Pack?

After I installed the Compatibility Pack on Office 2003 SP3 (XP Pro,
SP3) Excel 2007 file types are now listed at the end of the Save As
Dialog in Excel (2003)

--
Clif

"Howard Kaikow" wrote in message
...
"Steve Rindsberg" wrote in message
...


How could I determine whether I have the Compatibility Pack?





--
Clif

"Clif McIrvin" wrote in message
...
After I installed the Compatibility Pack on Office 2003 SP3 (XP Pro,
SP3) Excel 2007 file types are now listed at the end of the Save As
Dialog in Excel (2003)

Thanx.

Then I do not have the compatibility pack.

Searching at MSFT's support site, I found only 1 article that referred to
OfficeUpdate12.
Not sure that is relevant, not yet read.

Title is
How to troubleshoot failures updating your Office installation from the
Office Update Web site
http://support.microsoft.com/kb/304498

"Howard Kaikow" wrote in message
...
Searching at MSFT's support site, I found only 1 article that referred to
OfficeUpdate12.
Not sure that is relevant, not yet read.

Title is
How to troubleshoot failures updating your Office installation from the
Office Update Web site
http://support.microsoft.com/kb/304498

The article does indicate that OfficeUpdate12 directory will be in
Application Data, not Program Files.

To play safe, I'll have to try to remember to compile using
Office11\mso.dll, instead of Office12\mso.dsl.

In article , Howard Kaikow wrote:
"Steve Rindsberg" wrote in message
...
But the puzzle remains as to why some folkes have the Office12 mso.dll
and
others do not.

one possibility is that one might have to have a compiler, such as VB 6
or,
some other language, and not just office.

The Compatibility Pack may install the MSO.DLL version in question. Of
possibly one or another of the Office viewer apps (though not the
PowerPoint
viewer ... I just checked that).

I do not have the Compatibility Pack, at least I never asked for it to be
installed, not do I have any viewer on ANY of thse systems with Office 2000,
XP, or 2003.

How could I determine whether I have the Compatibility Pack?

Create or download (if you don't have Ofc2007) a PPTX or DOCX file.

Try to open it in the appropriate Office 2003 app. If it opens, you have the
compat. pack installed.

"Steve Rindsberg" wrote in message
...
Create or download (if you don't have Ofc2007) a PPTX or DOCX file.

Try to open it in the appropriate Office 2003 app. If it opens, you have
the
compat. pack installed.

Tried both Excel and Word.
Both asked whether I wanted to download the compatibility pack.