asked on

Problems connecting access database on network drive via ODBC. (UNC path is not an option)

Network drive is ok and valid in explorer, but is not valid in odbc profile. When database is chosen again in ODBC profile it is ok, but only until next reboot.

(Server is WIN 2003 and the client is WINDOWS 7 32 bit.)

ASKER CERTIFIED SOLUTION

robbe

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

jes12345

ASKER

UNC is unfortunately not an option. The error we get is: Error: directory or path is not valid (translated from Norwegian so maybe not correct) - this is not an issue on XP and seems to be a WIN7 issue only.

SOLUTION

robbe

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

puppydogbuddy

Win 7 is a 64 bit OS, running 64 Bit and 32 bit programs. You probably need to update your ODBC drivers for Win 7.
use "C:\Windows\SysWOW64\odbcad32.exe" to see if the drivers are installed there.
If not, there is a link below for MDAC 2.8. Download & install it from http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&displaylang=en
and it should install the correct drivers to the correct location.

jes12345

ASKER

This is probably not the issue because the odbc works fine until the next reboot. After a reboot the path is not valid anymore and the mdb file needs to be selected again.

puppydogbuddy

then, probably all you need to do is recreate the connection using the control panel .

jes12345

ASKER

I have tried to recreate the ODBC profile an recreate the mapping to the network drive. Same result.

SOLUTION

puppydogbuddy

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

jes12345