B
BMoore
A week ago Windows update so graciously updated my Windows 7 (32 bit) machine
with several 2007 Office and Windows security updates. Ever since then I
cannot open databases that are saved in mapped folder locations located on my
SBS 2003 machine. After troubleshooting it, here's what I know. The folder(s)
have been added as a Trused Location in Access, however for some reason
whenever I reboot the mapped drives are not showing up as "connected". They
show up with the little red 'x' on them.
Even if I view them in Explorer first and click on them so they show up
connected, (no red x) when I browse to them in an attempt to re-add the
folder as a Trusted Location, they show as disconnected inside Access. Once I
click on the folder, it connects and I don't even have to save the location
again, I simply have to click the folder so it connects. I can then cancel
out of everything and the database will open until I reboot again.
I know Office 2007 SP2 was one of the updates, but there were also several
others that might have been the culprit. I have tested this on several client
machines and so far the only 2 machines affected are both running Office 2007
and Windows 7. Can anyone confirm this and let me know if it is an Office
issue or a Win 7 issue?
Thanks,
with several 2007 Office and Windows security updates. Ever since then I
cannot open databases that are saved in mapped folder locations located on my
SBS 2003 machine. After troubleshooting it, here's what I know. The folder(s)
have been added as a Trused Location in Access, however for some reason
whenever I reboot the mapped drives are not showing up as "connected". They
show up with the little red 'x' on them.
Even if I view them in Explorer first and click on them so they show up
connected, (no red x) when I browse to them in an attempt to re-add the
folder as a Trusted Location, they show as disconnected inside Access. Once I
click on the folder, it connects and I don't even have to save the location
again, I simply have to click the folder so it connects. I can then cancel
out of everything and the database will open until I reboot again.
I know Office 2007 SP2 was one of the updates, but there were also several
others that might have been the culprit. I have tested this on several client
machines and so far the only 2 machines affected are both running Office 2007
and Windows 7. Can anyone confirm this and let me know if it is an Office
issue or a Win 7 issue?
Thanks,