Microsoft
Software
Hardware
Network
Question : Excel 2003 used not 2007
This just happened on code that was working fine for months (code in VBA of Access app)
I have both Excel 2003 (ver 11) and Excel 2007 (ver 12) installed on my
machine and I'm trying to instantiate Excel 12
Because a template is loaded that was made in 2007 and the automation application is 2003 then
a conversion readonly thing happens which is not good
I found the application instance was opening in 2003 (excel 11.0) even if I tell it to open in 12
Despite the version specific progID, ver 11 application is instantiated.
Dim xlApp As Object
Dim xlAppeeF As Object
Set xlApp = CreateObject("Excel.Applic
ation.12",
"")
Set xlAppeeF = xlApp.Application
Debug.Print xlAppeeF.Version < returns 11
? CreateObject("Excel.Applic
ation.12",
"").version < in Immediate window returns 11
I know both 11 and 12 have the same CSLIDs in the registry and I have changed some default curvers from office 11 to Office 12
No effect
Was early binding but reference was to Office12 excel
I am late binding now so references shouldn't effect it - In fact took out excel reference (which was to 12) - no effect
Google the heck out of this and found little help beyond what I have tried
excel 2003 and 2007 work fine standalone
I need to force automation to use 12 - how?
Answer : Excel 2003 used not 2007
one thing I didn't ry - Diagonose and repair in excel 2007 - took care of problem!
weird though
Random Solutions
Sorry, VMware GO doesn't currently support ESXi servers with multiple datastores.
How to copy a new copy of MS Access when the mdb is open
Can you load-balance a set of printers in samba?
Performance Monitor Wizard tells me log has been deleted create new
CBT for lotus notes 8.5 and sametime 8.5
802.1q trunk
2008 query in 2000
Adding Exchange 2010 server to an existing Exchange 2000
How to select all child DIVs except where class=...
What is message collison?