Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
"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.
Which QlikView and Oracle versions you are using?
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
Is there a different behavior if you're using 32bit connect?
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.
What is the data type of those problem fields in Oracle?
number field
I know , but which precision/scale?
it‘s only number。we are not define precision/scale。
Same problem on 32bit Connect??
I think it is a bug..