Excel changing UNC paths in shared workbook
up vote
2
down vote
favorite
Excel documents stored on network drive, for example, \networkdataExcelShared
Data workbook.xls contains tables with data entered into.
Report.xls contains UNC paths pointing to \networkdataexcelsharedworkbook.xls
Users enter data into data workbook.xls, and then see this reflected in report.xls- one workbook pulls data from the other.
One machine is giving issues. If this machine opens, edits and saves these documents, it changes the paths to reflect the local machine!
The machine has the path mapped as a drive, eg H: (\networkdataexcelshared), so opening a file from here will give the path H:data workbook.xls. I came across this article online which seems to talk about a similar issue-
The Knowledge Base article indicates that if a workbook is opened from a mapped drive, and the UNC >refers to that same drive, the UNC in the link is updated to the mapped drive designation.
Thinking that I had struck gold, I compared the set up (mapped drives, shortcuts etc) to another user's machine to identify a difference. The other machine has no issues but has the network location mapped exactly the same, as the same drive letter.
As a result this machine cannot be used to edit these shared workbooks, as if it saves it, it no longer points to the correct workbook on the network (eg it won't point to \networkdataexcelshared, but instread will refer to the location machine)
Any ideas?
microsoft-excel microsoft-excel-2010 network-shares
add a comment |
up vote
2
down vote
favorite
Excel documents stored on network drive, for example, \networkdataExcelShared
Data workbook.xls contains tables with data entered into.
Report.xls contains UNC paths pointing to \networkdataexcelsharedworkbook.xls
Users enter data into data workbook.xls, and then see this reflected in report.xls- one workbook pulls data from the other.
One machine is giving issues. If this machine opens, edits and saves these documents, it changes the paths to reflect the local machine!
The machine has the path mapped as a drive, eg H: (\networkdataexcelshared), so opening a file from here will give the path H:data workbook.xls. I came across this article online which seems to talk about a similar issue-
The Knowledge Base article indicates that if a workbook is opened from a mapped drive, and the UNC >refers to that same drive, the UNC in the link is updated to the mapped drive designation.
Thinking that I had struck gold, I compared the set up (mapped drives, shortcuts etc) to another user's machine to identify a difference. The other machine has no issues but has the network location mapped exactly the same, as the same drive letter.
As a result this machine cannot be used to edit these shared workbooks, as if it saves it, it no longer points to the correct workbook on the network (eg it won't point to \networkdataexcelshared, but instread will refer to the location machine)
Any ideas?
microsoft-excel microsoft-excel-2010 network-shares
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
Excel documents stored on network drive, for example, \networkdataExcelShared
Data workbook.xls contains tables with data entered into.
Report.xls contains UNC paths pointing to \networkdataexcelsharedworkbook.xls
Users enter data into data workbook.xls, and then see this reflected in report.xls- one workbook pulls data from the other.
One machine is giving issues. If this machine opens, edits and saves these documents, it changes the paths to reflect the local machine!
The machine has the path mapped as a drive, eg H: (\networkdataexcelshared), so opening a file from here will give the path H:data workbook.xls. I came across this article online which seems to talk about a similar issue-
The Knowledge Base article indicates that if a workbook is opened from a mapped drive, and the UNC >refers to that same drive, the UNC in the link is updated to the mapped drive designation.
Thinking that I had struck gold, I compared the set up (mapped drives, shortcuts etc) to another user's machine to identify a difference. The other machine has no issues but has the network location mapped exactly the same, as the same drive letter.
As a result this machine cannot be used to edit these shared workbooks, as if it saves it, it no longer points to the correct workbook on the network (eg it won't point to \networkdataexcelshared, but instread will refer to the location machine)
Any ideas?
microsoft-excel microsoft-excel-2010 network-shares
Excel documents stored on network drive, for example, \networkdataExcelShared
Data workbook.xls contains tables with data entered into.
Report.xls contains UNC paths pointing to \networkdataexcelsharedworkbook.xls
Users enter data into data workbook.xls, and then see this reflected in report.xls- one workbook pulls data from the other.
One machine is giving issues. If this machine opens, edits and saves these documents, it changes the paths to reflect the local machine!
The machine has the path mapped as a drive, eg H: (\networkdataexcelshared), so opening a file from here will give the path H:data workbook.xls. I came across this article online which seems to talk about a similar issue-
The Knowledge Base article indicates that if a workbook is opened from a mapped drive, and the UNC >refers to that same drive, the UNC in the link is updated to the mapped drive designation.
Thinking that I had struck gold, I compared the set up (mapped drives, shortcuts etc) to another user's machine to identify a difference. The other machine has no issues but has the network location mapped exactly the same, as the same drive letter.
As a result this machine cannot be used to edit these shared workbooks, as if it saves it, it no longer points to the correct workbook on the network (eg it won't point to \networkdataexcelshared, but instread will refer to the location machine)
Any ideas?
microsoft-excel microsoft-excel-2010 network-shares
microsoft-excel microsoft-excel-2010 network-shares
edited Jan 14 '15 at 11:29
Dave
23.2k74361
23.2k74361
asked Jan 14 '15 at 11:24
RASB
107515
107515
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
up vote
0
down vote
According to Microsoft, this is typical behavior established by the method the file is opened.
When a source data workbook is linked, the link is established based
on the way that the workbook was opened. If the workbook was opened
over a mapped drive, the link is created by using a mapped drive. The
link remains that way regardless of how the source data workbook is
opened in the future. If the source data file is opened by a UNC path,
the link does not revert to a mapped drive, even if a matching drive
is available. source
The likely cause is the file being opened differently on the various computers, some using the UNC and the other using a mapped path.
To add a solution to CharlieRB's answer: Try making a shortcut that uses the UNC path on the bothersome machine. It will require human discipline to open the file using that shortcut instead of whatever the user's current method. It would also behoove you to find out what their current method is and try to switch it to a UNC path at some point.
– Engineer Toast
Jan 20 '15 at 19:56
add a comment |
up vote
0
down vote
I have had this issue with a few clients. Both were using a mapped drive to access the file. One user would open the file, it would change the links to %appdata%XLSTART*corresponding file path to mapped drive*
I addressed this by making Excel open in the mapped drive for these users. Options, Advanced, General, At Startup, open all files in: (put the network path).
We use several mapped drives, often with Excel files from each. Should it be a specific one?
– RASB
Mar 12 '15 at 11:30
add a comment |
up vote
0
down vote
I usually open my files via the Explorer window, and got into this issue when I didn't notice the UNC path in the header bar; it used to be the full regular path. I set my shortcuts to the network folders, but they were all created as as UNC paths.
I opened up a fresh window, navigated to the network drive; all new links would now show up correctly. Killed all old Favorites; new ones now work fine.
Anil
add a comment |
up vote
0
down vote
Using a simple macro I tried to refresh the default file path each time before saving.
sub saveme()
Application.DefaultFilePath = "blablablabla$"
thisworkbook.save
end sub()
This seems to work.
add a comment |
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
According to Microsoft, this is typical behavior established by the method the file is opened.
When a source data workbook is linked, the link is established based
on the way that the workbook was opened. If the workbook was opened
over a mapped drive, the link is created by using a mapped drive. The
link remains that way regardless of how the source data workbook is
opened in the future. If the source data file is opened by a UNC path,
the link does not revert to a mapped drive, even if a matching drive
is available. source
The likely cause is the file being opened differently on the various computers, some using the UNC and the other using a mapped path.
To add a solution to CharlieRB's answer: Try making a shortcut that uses the UNC path on the bothersome machine. It will require human discipline to open the file using that shortcut instead of whatever the user's current method. It would also behoove you to find out what their current method is and try to switch it to a UNC path at some point.
– Engineer Toast
Jan 20 '15 at 19:56
add a comment |
up vote
0
down vote
According to Microsoft, this is typical behavior established by the method the file is opened.
When a source data workbook is linked, the link is established based
on the way that the workbook was opened. If the workbook was opened
over a mapped drive, the link is created by using a mapped drive. The
link remains that way regardless of how the source data workbook is
opened in the future. If the source data file is opened by a UNC path,
the link does not revert to a mapped drive, even if a matching drive
is available. source
The likely cause is the file being opened differently on the various computers, some using the UNC and the other using a mapped path.
To add a solution to CharlieRB's answer: Try making a shortcut that uses the UNC path on the bothersome machine. It will require human discipline to open the file using that shortcut instead of whatever the user's current method. It would also behoove you to find out what their current method is and try to switch it to a UNC path at some point.
– Engineer Toast
Jan 20 '15 at 19:56
add a comment |
up vote
0
down vote
up vote
0
down vote
According to Microsoft, this is typical behavior established by the method the file is opened.
When a source data workbook is linked, the link is established based
on the way that the workbook was opened. If the workbook was opened
over a mapped drive, the link is created by using a mapped drive. The
link remains that way regardless of how the source data workbook is
opened in the future. If the source data file is opened by a UNC path,
the link does not revert to a mapped drive, even if a matching drive
is available. source
The likely cause is the file being opened differently on the various computers, some using the UNC and the other using a mapped path.
According to Microsoft, this is typical behavior established by the method the file is opened.
When a source data workbook is linked, the link is established based
on the way that the workbook was opened. If the workbook was opened
over a mapped drive, the link is created by using a mapped drive. The
link remains that way regardless of how the source data workbook is
opened in the future. If the source data file is opened by a UNC path,
the link does not revert to a mapped drive, even if a matching drive
is available. source
The likely cause is the file being opened differently on the various computers, some using the UNC and the other using a mapped path.
answered Jan 14 '15 at 13:39
CharlieRB
20.4k44389
20.4k44389
To add a solution to CharlieRB's answer: Try making a shortcut that uses the UNC path on the bothersome machine. It will require human discipline to open the file using that shortcut instead of whatever the user's current method. It would also behoove you to find out what their current method is and try to switch it to a UNC path at some point.
– Engineer Toast
Jan 20 '15 at 19:56
add a comment |
To add a solution to CharlieRB's answer: Try making a shortcut that uses the UNC path on the bothersome machine. It will require human discipline to open the file using that shortcut instead of whatever the user's current method. It would also behoove you to find out what their current method is and try to switch it to a UNC path at some point.
– Engineer Toast
Jan 20 '15 at 19:56
To add a solution to CharlieRB's answer: Try making a shortcut that uses the UNC path on the bothersome machine. It will require human discipline to open the file using that shortcut instead of whatever the user's current method. It would also behoove you to find out what their current method is and try to switch it to a UNC path at some point.
– Engineer Toast
Jan 20 '15 at 19:56
To add a solution to CharlieRB's answer: Try making a shortcut that uses the UNC path on the bothersome machine. It will require human discipline to open the file using that shortcut instead of whatever the user's current method. It would also behoove you to find out what their current method is and try to switch it to a UNC path at some point.
– Engineer Toast
Jan 20 '15 at 19:56
add a comment |
up vote
0
down vote
I have had this issue with a few clients. Both were using a mapped drive to access the file. One user would open the file, it would change the links to %appdata%XLSTART*corresponding file path to mapped drive*
I addressed this by making Excel open in the mapped drive for these users. Options, Advanced, General, At Startup, open all files in: (put the network path).
We use several mapped drives, often with Excel files from each. Should it be a specific one?
– RASB
Mar 12 '15 at 11:30
add a comment |
up vote
0
down vote
I have had this issue with a few clients. Both were using a mapped drive to access the file. One user would open the file, it would change the links to %appdata%XLSTART*corresponding file path to mapped drive*
I addressed this by making Excel open in the mapped drive for these users. Options, Advanced, General, At Startup, open all files in: (put the network path).
We use several mapped drives, often with Excel files from each. Should it be a specific one?
– RASB
Mar 12 '15 at 11:30
add a comment |
up vote
0
down vote
up vote
0
down vote
I have had this issue with a few clients. Both were using a mapped drive to access the file. One user would open the file, it would change the links to %appdata%XLSTART*corresponding file path to mapped drive*
I addressed this by making Excel open in the mapped drive for these users. Options, Advanced, General, At Startup, open all files in: (put the network path).
I have had this issue with a few clients. Both were using a mapped drive to access the file. One user would open the file, it would change the links to %appdata%XLSTART*corresponding file path to mapped drive*
I addressed this by making Excel open in the mapped drive for these users. Options, Advanced, General, At Startup, open all files in: (put the network path).
answered Mar 12 '15 at 11:08
Tsmith
1
1
We use several mapped drives, often with Excel files from each. Should it be a specific one?
– RASB
Mar 12 '15 at 11:30
add a comment |
We use several mapped drives, often with Excel files from each. Should it be a specific one?
– RASB
Mar 12 '15 at 11:30
We use several mapped drives, often with Excel files from each. Should it be a specific one?
– RASB
Mar 12 '15 at 11:30
We use several mapped drives, often with Excel files from each. Should it be a specific one?
– RASB
Mar 12 '15 at 11:30
add a comment |
up vote
0
down vote
I usually open my files via the Explorer window, and got into this issue when I didn't notice the UNC path in the header bar; it used to be the full regular path. I set my shortcuts to the network folders, but they were all created as as UNC paths.
I opened up a fresh window, navigated to the network drive; all new links would now show up correctly. Killed all old Favorites; new ones now work fine.
Anil
add a comment |
up vote
0
down vote
I usually open my files via the Explorer window, and got into this issue when I didn't notice the UNC path in the header bar; it used to be the full regular path. I set my shortcuts to the network folders, but they were all created as as UNC paths.
I opened up a fresh window, navigated to the network drive; all new links would now show up correctly. Killed all old Favorites; new ones now work fine.
Anil
add a comment |
up vote
0
down vote
up vote
0
down vote
I usually open my files via the Explorer window, and got into this issue when I didn't notice the UNC path in the header bar; it used to be the full regular path. I set my shortcuts to the network folders, but they were all created as as UNC paths.
I opened up a fresh window, navigated to the network drive; all new links would now show up correctly. Killed all old Favorites; new ones now work fine.
Anil
I usually open my files via the Explorer window, and got into this issue when I didn't notice the UNC path in the header bar; it used to be the full regular path. I set my shortcuts to the network folders, but they were all created as as UNC paths.
I opened up a fresh window, navigated to the network drive; all new links would now show up correctly. Killed all old Favorites; new ones now work fine.
Anil
answered Jul 24 '15 at 16:06
Anil
1
1
add a comment |
add a comment |
up vote
0
down vote
Using a simple macro I tried to refresh the default file path each time before saving.
sub saveme()
Application.DefaultFilePath = "blablablabla$"
thisworkbook.save
end sub()
This seems to work.
add a comment |
up vote
0
down vote
Using a simple macro I tried to refresh the default file path each time before saving.
sub saveme()
Application.DefaultFilePath = "blablablabla$"
thisworkbook.save
end sub()
This seems to work.
add a comment |
up vote
0
down vote
up vote
0
down vote
Using a simple macro I tried to refresh the default file path each time before saving.
sub saveme()
Application.DefaultFilePath = "blablablabla$"
thisworkbook.save
end sub()
This seems to work.
Using a simple macro I tried to refresh the default file path each time before saving.
sub saveme()
Application.DefaultFilePath = "blablablabla$"
thisworkbook.save
end sub()
This seems to work.
answered Sep 19 at 12:46
user945687
1
1
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f864581%2fexcel-changing-unc-paths-in-shared-workbook%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown