close Warning: Can't synchronize with repository "(default)" (/var/svn/tolp does not appear to be a Subversion repository.). Look in the Trac log for more information.

Opened 18 years ago

Closed 17 years ago

#463 closed defect (fixed)

Problemas DBOpen

Reported by: ijgonzalez Owned by: danirus
Priority: highest Milestone:
Component: DataBase Version: head
Severity: blocker Keywords:
Cc:

Description

Hello,

The TOL version 1.1.5 of january 16 of 2007 give me problems using DBOpen function.

I use
Real DBOpen(Alias,User,Password);

The error is this:
ERROR: [3] No se pudo conectar con el alias 'SSCM02'.

This error don't occur in the tol version 1.1.4 of december the 4 of 2006.

Change History (4)

comment:1 Changed 18 years ago by ijgonzalez

Sorry for my incomplete description.

The error occurs when i try to connect to an SQL Server Data Base.

comment:2 Changed 18 years ago by danirus

Status: new → assigned

comment:3 Changed 18 years ago by danirus

Hi Iván,

Thanks for reporting this bug.
I've patched libtolodbc.c to resolve it, and it will be available in the next Tol Main Trunk recompilation. The error was not in fact an error, altought it was treated as such.

Here is a longer explanation:
After doing SQLConnect to a SQL Server ODBC conn, we get a SQL_SUCCESS_WITH_INFO SQLRETURN code. It could be considered as SQL_SUCCESS, but ODBC maintainers suggests to find the reason around that and to inform the user. Tol-ODBC Driver's GetDiagRec method will be customized to properly give back an explanation to the user.

Apart from that, Tol-ODBC Driver delivered with Tol v1.1.4 ignores SQL_SUCCESS_WITH_INFO after SQLConnect, and accept it as a normal SQL_SUCCESS.

Daniel

comment:4 Changed 17 years ago by danirus

Resolution: → fixed
Status: assigned → closed
Note: See TracTickets for help on using tickets.