- Thread Author
- #1
I feel like a fish out of water on this issue.
We are calling a legacy VBA function in Access 2010 to try to read filed information about files saved to our SharePoint site. When this code is run in Access 2010 running on Windows XP the function identifies the file and indicates that the file exists and will return the last modified date and other information about the file. However, when the same VBA function is called in Access 2010 running on Windows 7 the function fails to find the existing folder or the existing file. Both machines are connected to the same network and the network access is the same. The only variable in this situation is Windows XP vs Windows 7.
If we provide the url to the same path in Windows Explorer on the Windows 7 machine, it finds the file and asks if we want to open or save the file. The same is true if we enter the same path in the command window (Start/Run).
We also have functionality in this same application that attempts to use a OutPutTo intrinsic VBA function to create an Excel file on the SharePoint site. This functionality works in the Windows XP platform but fails when run on the Windows 7 platform.
I am trying to find any setting in Windows 7 that might be preventing Windows from interpreting the URL correctly or any other setting that would prevent the VBA code from working in the Windows 7 platform.
Any suggestions would be appreciated.
We are calling a legacy VBA function in Access 2010 to try to read filed information about files saved to our SharePoint site. When this code is run in Access 2010 running on Windows XP the function identifies the file and indicates that the file exists and will return the last modified date and other information about the file. However, when the same VBA function is called in Access 2010 running on Windows 7 the function fails to find the existing folder or the existing file. Both machines are connected to the same network and the network access is the same. The only variable in this situation is Windows XP vs Windows 7.
If we provide the url to the same path in Windows Explorer on the Windows 7 machine, it finds the file and asks if we want to open or save the file. The same is true if we enter the same path in the command window (Start/Run).
We also have functionality in this same application that attempts to use a OutPutTo intrinsic VBA function to create an Excel file on the SharePoint site. This functionality works in the Windows XP platform but fails when run on the Windows 7 platform.
I am trying to find any setting in Windows 7 that might be preventing Windows from interpreting the URL correctly or any other setting that would prevent the VBA code from working in the Windows 7 platform.
Any suggestions would be appreciated.
