Hi there. I've got some code that does various things, among them,
opening an Excel file. Here's a little snippet of relevant code:

FilePath = "\\servername\share\folder\"
FileName = "template.xls"

Set aXL = CreateObject("Excel.Application")
With aXL
.Visible = False
.Workbooks.Open FilePath & FileName
End With

Here's the problem. When I run this on a machine using Office 2000, it
works just fine. When I run in on a machine using Office 2003, it gives
me this error:

"Open Method of Workbooks class failed"

Now... on Office 2003, if I change the "FilePath" to the *mapped*
network drive for the same folder (i.e. "S:\folder\"), then the code
works just fine. It's only when I try to use the full network path of
the same location that the code fails. But it works either way on
Office 2000. I need to be able to use the full path so this can be run
on different machines that may not have the same share mapped to the
same drive letter.

My question is, is this due to some kind of new network security
setting in Office 2003? If not, is there something else that would be
causing this?

WATYF

Hi,

using WinXP, Office2003

I cannot reproduce the behaviour. In other words, I am able to open
workbook using this statement:

workbooks.Open filename:="\\unxcz0002\common\controlling\TC file
specification.xls"

Are you sure you have correct path?

Regards,
Ivan

Yeah... I'm sure on the path. And if I change it to a bad path, I get a
totally different error (file cannot be found. check your spelling,
etc.)

Btw, when you ran your test, did you run it from within Excel and just
use the Workbooks.Open method, or did you run it from somewhere else
(VB app, Word, etc) and create a late-bound instance of Excel (like in
my example)?


WATYF

Hi,

I used late binding, Word.

Regards,
Ivan