Hi,

I've got a very weird ODBC problem and the log file mentions this: DIAG
[IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr
failed (0)

The situation is the following:

* I've got several Windows 2000 and Windows XP PCs. Each PC has Access
2003, some also Access 2000.
* I've one legacy Access 2000 Frontend which connects to an SQL Server >
everything works fine on every machine.
* I've written an Access 2003 Frontend which connects to an SQL Server
Backend > works fine on some, and not so fine on others!? On those I'm
getting ODBC errors.
* It doesn't matter if there's only Access 2003 or if there's Access
2000 as well. It works on some where both are, and not on others.
* The problem seems to be inherent to the machine, not the user! The
user from a 'bad' PC can log on a 'good' PC and the Access app works.
The user from a 'good' PC can log on a 'bad' PC and the Access app
doesn't work neither!?
* I've tried to re-install Access on the 'bad' PCs. No change (which
isn't surprising since the ODBC causes the errors ...).

The PCs look absolutely the same! What could cause this ODBC behavior??
Can I 're-install' the ODBC drivers? Or what else could I do? I really
need these apps working on ALL machines ...

Any help is GREATLY appreciated!

Jerome

Note this may be a wild goose, the error you are tracking down.
I see this all the time in ODBC traces, it is normal. Typically most
drivers don't support every connection attribute that the client application
throws at it.

However I did find this in the KB, it might be related ->

http://support.microsoft.com/kb/822841

I suspect you are getting other ODBC errors, post these as well.

--
Matt Neerincx [MSFT]

This posting is provided "AS IS", with no warranties, and confers no rights.

Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Jerome" <subliminal.void@gmail.com> wrote in message
news:uZeUveTuFHA.1264@TK2MSFTNGP12.phx.gbl...
> Hi,
>
> I've got a very weird ODBC problem and the log file mentions this: DIAG
> [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
> (0)
>
> The situation is the following:
>
> * I've got several Windows 2000 and Windows XP PCs. Each PC has Access
> 2003, some also Access 2000.
> * I've one legacy Access 2000 Frontend which connects to an SQL Server >
> everything works fine on every machine.
> * I've written an Access 2003 Frontend which connects to an SQL Server
> Backend > works fine on some, and not so fine on others!? On those I'm
> getting ODBC errors.
> * It doesn't matter if there's only Access 2003 or if there's Access 2000
> as well. It works on some where both are, and not on others.
> * The problem seems to be inherent to the machine, not the user! The user
> from a 'bad' PC can log on a 'good' PC and the Access app works. The user
> from a 'good' PC can log on a 'bad' PC and the Access app doesn't work
> neither!?
> * I've tried to re-install Access on the 'bad' PCs. No change (which isn't
> surprising since the ODBC causes the errors ...).
>
> The PCs look absolutely the same! What could cause this ODBC behavior??
> Can I 're-install' the ODBC drivers? Or what else could I do? I really
> need these apps working on ALL machines ...
>
> Any help is GREATLY appreciated!
>
> Jerome