J
Johnny Eager
I have created a VBA macro in Word which extracts data from Word, separates
the data, launchs Excel, opens a template, and populates fields. I have the
process reversed (also written in Word). It works flawlessly in all versions
of compatible versions of Windows Office AND in Mac OS 9.2 (Office 98 and
2001) and in all test versions of Mac OS X.
The problem is that on Mac OS X with Office X (in all of the client's
machines) the program crashes just after Excel is launched and the template
is opened. It just kills Word and leaves Excel Open.
We have tested the program on all versions of Macs from iBook 400 to G3
Tower to G4 PowerBook and G4 Towers.
Here is an example of the Code where it crashes:
====
Set xlApp = CreateObject("Excel.Application")
With xlApp
.Workbooks.Open FileName:=sXLtmp, Editable:=True
.ActiveWorkbook.SaveAs FileName:=sXLdoc
.Visible = True
End With
====
All the variable are fine.
All the programs are updated.
All the permissions are corrected.
Again, it works flawlessly on all versions of Office and on all machine I
use to test. But crashes the clients machines.
Question: I have not tested on a dual processor. Can that make a difference
in Microsoft Automation?
I know the business has a site license, can there be some sort of network
checking that would cause this problem? I have unplugged the network. And it
does open Excel.
I would appreciate some input on this perplexing problems.
Thank you very much,
je
the data, launchs Excel, opens a template, and populates fields. I have the
process reversed (also written in Word). It works flawlessly in all versions
of compatible versions of Windows Office AND in Mac OS 9.2 (Office 98 and
2001) and in all test versions of Mac OS X.
The problem is that on Mac OS X with Office X (in all of the client's
machines) the program crashes just after Excel is launched and the template
is opened. It just kills Word and leaves Excel Open.
We have tested the program on all versions of Macs from iBook 400 to G3
Tower to G4 PowerBook and G4 Towers.
Here is an example of the Code where it crashes:
====
Set xlApp = CreateObject("Excel.Application")
With xlApp
.Workbooks.Open FileName:=sXLtmp, Editable:=True
.ActiveWorkbook.SaveAs FileName:=sXLdoc
.Visible = True
End With
====
All the variable are fine.
All the programs are updated.
All the permissions are corrected.
Again, it works flawlessly on all versions of Office and on all machine I
use to test. But crashes the clients machines.
Question: I have not tested on a dual processor. Can that make a difference
in Microsoft Automation?
I know the business has a site license, can there be some sort of network
checking that would cause this problem? I have unplugged the network. And it
does open Excel.
I would appreciate some input on this perplexing problems.
Thank you very much,
je