Icon View Incident Report

Serious Serious
Reported By: Fernando Dias
Reported On: 6/27/2008
For: Version 2.00 Build 2
# 2690 ODBC Driver Causing ODBC Call Failed Error When Opening Table in Access with TimeStamp Column

Opening the following table "CatPrecos" results in the following string in all of the columns:

"#Nome?" = "#Name?"

and causes the following error:

"ODBC --falhou a chamada" = "ODBC --Call failed"

CREATE TABLE "CatPrecos"
(
"CodFornecedor" INTEGER,
"Codigo" VARCHAR(13) COLLATE "PTG",
"Fim" TIMESTAMP,
"Descricao" VARCHAR(20) COLLATE "PTG",
"PCustoLiq" FLOAT,
"PctMargemLiq" FLOAT,
"MargemLiq" FLOAT,
"PVPLiq" FLOAT,
"PCustoTotal" FLOAT,
"PctMargemTotal" FLOAT,
"MargemTotal" FLOAT,
"PVPTotal" FLOAT,
"PVP" FLOAT,
"Taxas" FLOAT,
"TaxaXP" DECIMAL(20,2),
CONSTRAINT "PrimaryKey" PRIMARY KEY ("CodFornecedor", "Codigo", "Fim")
)



Comments Comments
This error was caused by the fact that the ODBC driver was not setting the session's ODBC compliance level correctly according to what the application wanted (in this case ODBC 2). Therefore, date, time, and timestamp columns were returning the data in the wrong format.


Resolution Resolution
Fixed Problem on 6/29/2008 in version 2.01 build 1


Products Affected Products Affected
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial

Image