469,568 Members | 1,413 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,568 developers. It's quick & easy.

Problems with ODBC access since XP SP2 upgrade

I've got an app written with Access XP that was deployed 2 years ago
using a PostgreSQL backend database through an internet connection.
Recently a client upgraded to XP Service Pack 2. After the upgrade she
was unable to connect to the remote database, getting the error:

Unable to connect to remote database File Name=C:\Program Files\Common
Files\ODBC\Data Sources\PostgresCNI.dsn Error message: The file is not
a
valid compound file.

I did some research and found people recommending the connection
string use 'FileDSN=<dsn file>' instead of 'File name=<dsn file>'

So I changed it from:

Set conn = New ADODB.connection
conn.Open "File Name=C:\Program Files\Common Files\ODBC\Data
Sources\PostgresCNI.dsn"

to

Set conn = New ADODB.connection
conn.Open "FileDSN=C:\Program Files\Common Files\ODBC\Data
Sources\PostgresCNI.dsn"

Now the app gives this error:

This file is located outside your intranet or on an untrusted site.
Microsoft Acess will not open the file due to potential security
problems.
To open the file, copy it to your machine or an accessible network
location.

What happened in SP2 that's preventing remote ADODB connections?
Nov 13 '05 #1
1 2390
Windows XP SP2 included a large new security component. My understanding is
that some of it can be tweaked. A google on Windows XP SP2 security should
turn up more information than you could ever wish to know.
Darryl Kerkeslager
"Randall Perry" <rg*@systame.com> wrote in message
news:fa**************************@posting.google.c om...
I've got an app written with Access XP that was deployed 2 years ago
using a PostgreSQL backend database through an internet connection.
Recently a client upgraded to XP Service Pack 2. After the upgrade she
was unable to connect to the remote database, getting the error:

Unable to connect to remote database File Name=C:\Program Files\Common
Files\ODBC\Data Sources\PostgresCNI.dsn Error message: The file is not
a
valid compound file.

I did some research and found people recommending the connection
string use 'FileDSN=<dsn file>' instead of 'File name=<dsn file>'

So I changed it from:

Set conn = New ADODB.connection
conn.Open "File Name=C:\Program Files\Common Files\ODBC\Data
Sources\PostgresCNI.dsn"

to

Set conn = New ADODB.connection
conn.Open "FileDSN=C:\Program Files\Common Files\ODBC\Data
Sources\PostgresCNI.dsn"

Now the app gives this error:

This file is located outside your intranet or on an untrusted site.
Microsoft Acess will not open the file due to potential security
problems.
To open the file, copy it to your machine or an accessible network
location.

What happened in SP2 that's preventing remote ADODB connections?

Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

8 posts views Thread by Philip Wright | last post: by
12 posts views Thread by Remco Groot Beumer | last post: by
1 post views Thread by Harmony407 | last post: by
1 post views Thread by steven_nospam at Yahoo! Canada | last post: by
4 posts views Thread by guiromero | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.