[dba-SQLServer] ODBC Connection error - More Info

MartyConnelly martyconnelly at shaw.ca
Fri Nov 3 14:54:33 CST 2006


Jet Service Packs were seperated from the MDAC install after MDAC 2.5
Jet 8 SP available as seperate install from here
http://msdn.microsoft.com/data/ref/mdac/downloads/

Various OS install a set version of MDAC ie WinXP SP2 installs MDAC 2.8
However Access 2000 installs Jet SP4
and Access 2003 JetSP7 and Access 2007 Jet SP8

You might want to check if he is running under Admin or User privileges.

Also for further info
How to keep a Jet 4.0 database in top working condition
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q303528

John Skolits wrote:

>I assume you mean the latest MDAC? Or is there something else that would
>make sure we had the same one.
>
>-----Original Message-----
>From: dba-sqlserver-bounces at databaseadvisors.com
>[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of
>MartyConnelly
>Sent: Friday, November 03, 2006 1:53 PM
>To: dba-sqlserver at databaseadvisors.com
>Subject: Re: [dba-SQLServer] ODBC Connection error - More Info
>
>Are you both running the same Jet Service Pack
>See
>http://www.microsoft.com/data
>
>John Skolits wrote:
>
>  
>
>>No, not really.
>>
>>I was just on the phone with him and it seems there is a compile issue. 
>>    
>>
>
>  
>
>>I have two, almost identical functions. One works from the immediate window
>>and the other gives him a compile error. Although the program compiles
>>correctly.
>>I'll first have him uncompile\recompile and repair. Yet, I'm running the
>>exact same version on an Access 2000 version with no problems.
>>
>>The other option would be to have him reinstall Access 2003.
>>
>>
>>As far as the ODBC error, I'm finding that when he manually reconnects the
>>Trusted Connection is automatically set to True. When I relink through code
>>that I wrote, I always set the trusted connection to False and have never
>>had a problem on the many applications I have written. Except on his PC.
>>
>>For now, I think it's his installation, although not positive.
>>
>>
>>
>>
>>-----Original Message-----
>>From: dba-sqlserver-bounces at databaseadvisors.com
>>[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim
>>Lawrence
>>Sent: Friday, November 03, 2006 11:51 AM
>>To: dba-sqlserver at databaseadvisors.com
>>Subject: Re: [dba-SQLServer] ODBC Connection error - More Info
>>
>>Hi John:
>>
>>Would his password have a special character in it that is not allowed?
>>
>>Jim 
>>
>>-----Original Message-----
>>From: dba-sqlserver-bounces at databaseadvisors.com
>>[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John
>>Skolits
>>Sent: Friday, November 03, 2006 7:10 AM
>>To: dba-sqlserver at databaseadvisors.com
>>Subject: Re: [dba-SQLServer] ODBC Connection error - More Info
>>
>>I'm also getting the following error when trying to run a few queries.
>>
>>Connection Failed:
>>SQL State '28000'
>>Sql Server Error: 18452
>>{Microssoft][Sql Server Driver][Sql Server]Logon Failed for user '(null)'
>>Reason: Not associated with a trusted cSql Server Conenction.
>>
>>
>>-----Original Message-----
>>From: dba-sqlserver-bounces at databaseadvisors.com
>>[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John
>>Skolits
>>Sent: Friday, November 03, 2006 9:43 AM
>>To: dba-sqlserver at databaseadvisors.com
>>Subject: [dba-SQLServer] ODBC Connection error
>>
>>I'm having this ODBC connection error that's driving me nuts.
>>
>>The application  is written in Access 2000. The User's Pc is Access 2003.
>>MDAC 2.8 is his latest version.
>>
>>There have been times where the application has run fine, then I make a few
>>changes and the user can't connect to the tables.
>>The only way to make it work is to go in an manually relink every table on
>>his PC. If I do it on my development PC, or any other PC for that matter,
>>    
>>
>he
>  
>
>>can't open the tables.
>>
>>I ran a Pass thru query on his PC with a new DSN I created and a connection
>>string like:
>>ODBC;DRIVER=SQL Server;SERVER=otto;UID=User;PWD=User;DATABASE=ssa_erpdb
>>
>>I then received an error message like :
>>ODBC error ..... ODBC;DRIVER=SQL Server;SERVER=otto;UID=reports;PWD=repo_'
>>
>>Notice how it truncated the string.
>>
>>So it looks like It's a problem on his PC. 
>>
>>I tried a myriad of things. Is there any Service releases or anything
>>    
>>
>anyone
>  
>
>>has heard of that may fix this issue before I spend weeks trying to find a
>>work around.
>>
>>John
>>
>> 
>>    
>>

-- 
Marty Connelly
Victoria, B.C.
Canada




More information about the dba-SQLServer mailing list