use 'OLEDB CONNECT 64bit oracle happen 1 change 1.00000000000000000000000000000000000

[#1]

When I user ''OLEDB CONNECT TO [Provider=OraOLEDB.Oracle.1;User ID=fbi_dw;Data Source=mic133] (XPassword is DORLQTRMITccWcBHBDZOXGC);'' to connect oracle .I reload again ,my date has someting error. how to solve it

[#2]

"FBI_DW"."DIM_CALENDAR" is a table 。 now  I use  OLEDB beacuse  it’s more faster。I used to connecting ODBC is ok。BUT now I have to use OLEDB.Do you have any other way  to solve this  problem, beacuse we have a lot of  table  and  qvw,it will take us a lot of time.

[rbecher]

Which QlikView and Oracle versions you are using?

[#4]

my QlikView  versions  is QlikView x64   10.00.8935.7  SR2，and

Oracle versions is oracle 10.2.0.1.0。

Windows Server 2003 Service Pack 2 for x64 Editions

[rbecher]

Is there a different behavior if you're using 32bit connect?

[#6]

Hi, if I connect with oracle provider for oledb  some field is 'fixed to 14 decimals '  in number format settings   ,This is not what I want.

but I connect with  microsoft oledb provider for oracle  some field is 'number 14 precision '  in number format settings   ,this is ok.

[rbecher]

What is the data type of those problem fields in Oracle?

[#8]

number  field

[rbecher]

I know , but which precision/scale?

[#10]

it‘s only number。we are not define precision/scale。

[rbecher]

Same problem on 32bit Connect??

I think it is a bug..