Solved Inactive mapped drive within program until manual selection

[dianedebuda]

Running an Access97 app that has Mail Merge automation to Word97. (Please refrain from "need to update" - not going to happen; VMware player + XP Mode works, but prefer running native Win7 if possible for Home Prem laptop user). To get the Mail Merge to work, msaccess & winword have to run at XP SP3 compatibility. So far, so good. Odd thing involves the mapped network drive where data is located. I get a "not found" from within Access even if I've already accessed the mapped drive from Explorer. If I manually find the database from within Access by walking the structure, all is good until I reboot - even if I close the mdb & reopen it with a shortcut. The mru list within Access fails - I must manually walk the dir tree from within Access after a reboot. Is this Access97 specific behavior or has it been dealt with for other programs?

Googling found How to make elevated programs recognize network drives; I added the EnableLinkedConnections registry entry, but the behavior was unchanged.

 

[dianedebuda]

I forgot to mention: this inactive mapped situation only occurs with compatibility selected. Network drive fine without, but then can't use mail merge.

 

[dianedebuda]

For anyone else having to deal with antiques...

Adding this registry setting solved the problem for me: Some Programs Cannot Access Network Locations When UAC Is Enabled.

In a nutshell, the user's mapped drive is not seen by the Admin account by default. The reg entry allows it.

This is basically the same as I found in the first post. Maybe I didn't reboot before retry? Anyhow, works now.