Excel 2003 automated instead of Excel 2007

[Bert]

Hi,

I have Excel 2003 and 2007 installed on the same machine.

I'm trying to automate Excel 2007, but everything I seem to do ends up in
Excel 2003.

I have a file (XLSX) which was made in Excel 2007 and I'm trying to open it
programmatically. But since the file has more than 65K rows, I keep getting
a trunction warning and after the file opens I have only the first 65K rows.

I use late binding. I tried acquiring the Application object using
Excel.Application and Excel.Application.12 prog IDs. I also tried early
binding (adding the Office 12 library and the Excel library) but they all
result in the same problem.

Any idea would be greatly appreciated.

Thanks!!!

Bert.

 

[Mark Ivey]

Without going in to code specifics...

This link explains how to open a file with VBScript. In many cases you can
apply VBScript right inside your procedure or module.

This link should give you some pointers on how to go about opening a
specified file with what ever version Excel you choose (you will need to
specify the path for your version of Excel 2007).

http://www.visualbasicscript.com/m_549/mpage_1/key_/tm.htm#549

Mark

 

[Jim Rech]

I find Excel 2003 and 2007 like to each take control of "Excel.Application".
He who registers last registers best.

That control takes the form of this registry entry:

HKEY_CLASSES_ROOT\CLSID\{00024500-0000-0000-C000-000000000046}\LocalServer32

When you open Regedit.exe to this key you see two entries in the right
panel. The "LocalServer32" entry seems to be the controling entry but its
value is in some jibberish that I don't know how to edit. But if
"LocalServer32" is not present I find that "(Default)" is used, and that is
editable.

So if you want to switch the Excel version that automates:

Rename "LocalServer32" to say "LocalServer32x". Then edit Default to point
to the Excel.exe you want to run.

 

[Bert]

Mark,

Thanks for your reply.

Executing Excel through Shell will not do. I need the COM object model
behind the workbook in my application, not as an Excel macro.

Unfortunately, the problem remains.

Thanks