Search found 8 matches

by LeoPrates
Wed 28 Jun 2017 20:43
Forum: dbExpress driver for Oracle
Topic: Date 30/12/1899
Replies: 1
Views: 33802

Date 30/12/1899

Hi I'm using dbExpress driver for Oracle Standard, version 6.10.15 and the empty dates are being returned as 30/12/1899 (Brazilian format, I from Brazil).
Can you correct via CRSQLConncetion parameters?
by LeoPrates
Fri 02 Jun 2017 18:54
Forum: dbExpress driver for InterBase & Firebird
Topic: Not Found Driver DevartInterbase
Replies: 1
Views: 48951

Not Found Driver DevartInterbase

Hello. After installing the dbExpress driver for Interbase Standard version 2.70.29 is not appearing in the "DevartInterbase" option in the TCRSQLConnection property driver.

Before, you had already installed the dbExpress driver for Oracle Standard along with the TCRSQLConnection, and then run the dbxida270.exe not added to the Interbase Driver option.

If I install a trial version and added the driver.

I'm using Delphi Berlin, update 2.
by LeoPrates
Thu 12 Jan 2017 11:37
Forum: dbExpress driver for Oracle
Topic: Data Mapping SELECT MAX(NUMBER_FIELD)
Replies: 2
Views: 11886

Re: Data Mapping SELECT MAX(NUMBER_FIELD)

Hi, again.

Sorry but I found the solution and it's very simple.
I'm migrating a Delphi 7 project to Delphi Berlin, and before those fields were created with the FieldKind property as fkData, just change to fkCalculated that resolved. :oops:
Thank you.
by LeoPrates
Wed 11 Jan 2017 13:25
Forum: dbExpress driver for Oracle
Topic: Data Mapping SELECT MAX(NUMBER_FIELD)
Replies: 2
Views: 11886

Data Mapping SELECT MAX(NUMBER_FIELD)

Hi.

I have a problem, I have Number(10) Fields in Oracle and I use it in my application doing "Select MAX(FIELD_NUMBER_10) From Table" and in my ClientDataSet these fields are TIntegerField but are giving the message "expecting: Integer, Actual: Float" But I need to keep them as TIntegerField.


I am currently using the parameters:
Params.Values['BCDPrecision'] := '0';
Params.Values['FloatPrecision'] := '38';
Params.Values['IntegerPrecision'] := '38';

Is there any data mapping parameter that can fix this?
by LeoPrates
Tue 27 Dec 2016 17:31
Forum: dbExpress driver for Oracle
Topic: Data Maping Expecting: Integer, Actual: Float
Replies: 5
Views: 14092

Re: Data Maping Expecting: Integer, Actual: Float

I found the problem ...

Running the select * from v$version command saw that the error is in installations of version 11.2.0.1.0.

In version 11.2.0.4.0 it seems to be right to treat the Number (5) columns as TSmallIntField.
by LeoPrates
Tue 27 Dec 2016 15:47
Forum: dbExpress driver for Oracle
Topic: Data Maping Expecting: Integer, Actual: Float
Replies: 5
Views: 14092

Re: Data Maping Expecting: Integer, Actual: Float

Working with two oracle installations.

When I import the columns to the ClientDataset in an Oracle installation the column is being created as TFMTBCDField of Precision 32, and in another installation it is important as TFMTBCDField of 5, but in both databases the column is Number (5).
What is the criteria for columns of the same type to be different in clientdataset?
You looked at the dba_tab_columns, user_tab_columns, and all_tab_columns managements tables of the two databases and found no difference between them.

Any ideas on that?
by LeoPrates
Mon 26 Dec 2016 17:07
Forum: dbExpress driver for Oracle
Topic: Data Maping Expecting: Integer, Actual: Float
Replies: 5
Views: 14092

Re: Data Maping Expecting: Integer, Actual: Float

Thanks for the feedback.

Saying that in your tests everything is ok did not solve my problem, I also need to keep the field as TIntegerField, I can not change it.

Any other suggestions for me to test?
by LeoPrates
Fri 23 Dec 2016 10:53
Forum: dbExpress driver for Oracle
Topic: Data Maping Expecting: Integer, Actual: Float
Replies: 5
Views: 14092

Data Maping Expecting: Integer, Actual: Float

Using Oracle 11g Release 2.
In an sql I have Number (10) and Number (5) fields.
In the ClientDataSet both are as TIntegerField, but when opening the search shows "Type mismatch for field 'FIELD', expecting: Integer actual: Float".

The problem is in the Number (5) field. The Number (10) field works fine as TIntegerField.


with SQLConnection1 do
begin
Connected := False;
DriverName := 'DevartOracle';
GetDriverFunc := 'getSQLDriverORA';
Params.Values['DataBase'] := 'database';
Params.Values['User_Name'] := 'username';
Params.Values['Password'] := '*****';
Params.Values['BlobSize'] := '-1';
Params.Values['LocaleCode'] := '0000';
Params.Values['Oracle TransIsolation'] := 'ReadCommited';
Params.Values['RoleName'] := 'Normal';
Params.Values['LongStrings'] := 'True';
Params.Values['EnableBCD'] := 'False';
Params.Values['FetchAll'] := 'False';
Params.Values['UseUnicode'] := 'False';
Params.Values['BCDPrecision'] := '0';
Params.Values['FloatPrecision'] := '38';
Params.Values['IntegerPrecision'] := '38';
end;