I have a developer who is attempting to open an Excel workbook via VB6.
He dims and later sets the appropriate variable to an Excel.Application. He
does the same for a workbook object. The code is running off a server, with a
mapped drive of W. To troubleshoot and test, he uses Dameware to log into the
server. Then he runs his application. When he goes to open a workbook off
our LAN, it returns an error #1004.

He copied the project to his local PC. His mapped drive to the server is now
X. No big deal, he changes the path to X:\... The code works on his local PC.

Anyone seen any issues with opening a workbook off the LAN with a mapped
drive?

In case this helps:
- Changing the path to use UNC does not solve the issue.
- When using the immediate window right after the 1004 error pops up, we ran
a vba.dir(<path) and the filename is returned, so the file is on the
filesystem.
Hard codind the path in the Workbooks.Open() method does not solve the
problem either.
- The PC and the server both use VB6 and Excel2002 SP3.
- This issue immediately arose when Excel on the server was upgraded from
Excel97 just 2 days ago.