Access databases on a mapped network drive generates run time error 3044 first time

[virgilio]

One of my Access databases that is on a mapped network drive generates run time error 3044 when I connect to it for the first time.

The full error is

Run-time error '3044':
'G:\path\to\file' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.

This error is easily overcome by opening file explorer and clicking the mapped drive, which defaults to disconnected with a red 'x' so that it turns green.



Is there anyway to make Access open that connection when file opens without having to go to explorer and click into it first?

[Micron]

clicking the mapped drive, which defaults to disconnected with a red 'x' so that it turns green.

You make that sound like a Windows problem if the user is losing a connection to a network drive. However if the issue is the drive letter because all users are not mapped to G then use UNC path instead: \\serverName\folder1\folder2...

[June7]

Determine why drive does not connect automatically and resolve. Did you web search topic?

https://sacomedia.com/solved-windows...-reconnecting/

https://answers.microsoft.com/en-us/...7-d49e3bb5899d

Or as Micron suggested, use UNC path in database connections. Is this involving linked table object? Can set links by navigating through Network or use VBA to set links with UNC path. https://stackoverflow.com/questions/...66065#66866065

[virgilio]

Thanks for your responses. I got called to a different project and probably won't be able to address this before Friday.

I'll try June's suggestion of setting the source to full UNC in VBA.

I'll mark as solved but maybe re-open it if related issues persist.