I had a procedure that called to open a workbook:

sAddress = \\Servername\Part\Folder1\Folder2\Folder3\File.xls

Workbooks.Open sAddress, 0, False

This worked perfectly well in Excel 2000, but after upgrading to 2003, it
kicks back an error stating Method 'Open' of object 'Workbooks' failed.

I checked and the file does exist where the address is, and can be opened
manually. I did some testing and I was able to figure out that after a
certain number of folders deep, the open function no longer worked. Is there
a maximum length allowed for the file path now?
--
*********************
J Streger
MS Office Master 2000 ed.
MS Project White Belt 2003

Never mind. Figured out my own problem. Excel 2003 is a little more strict on
sheet names, and the files I was opening had invalid sheet names which are
causing the issues.

--
*********************
J Streger
MS Office Master 2000 ed.
MS Project White Belt 2003



"J Streger" wrote:

I had a procedure that called to open a workbook:

sAddress = \\Servername\Part\Folder1\Folder2\Folder3\File.xls

Workbooks.Open sAddress, 0, False

This worked perfectly well in Excel 2000, but after upgrading to 2003, it
kicks back an error stating Method 'Open' of object 'Workbooks' failed.

I checked and the file does exist where the address is, and can be opened
manually. I did some testing and I was able to figure out that after a
certain number of folders deep, the open function no longer worked. Is there
a maximum length allowed for the file path now?
--
*********************
J Streger
MS Office Master 2000 ed.
MS Project White Belt 2003