------------------------------
Anna lisa Coppola
Developper
Dedalus Spa
------------------------------
Ciao Annalisa,
I would check Uniface driver version first:
in your post you mentioned U7 driver but based on PAM there are 4 different U7 driver versions (U7.0, U7.1, U7.2, U7.3). The one correct for Oracle 12.2 depends from version R1 or R2 of Oracle 12. My guess is the right one for you should be U7.2 based on the fact you mentioned 64bit.
Second: you can do a small test having a "Load definition" from that Oracle table into a temporary Uniface application model to see how Uniface do by itself against that table; building a quick form you can check if the problem is still there.
Let us know if your problem is solved and which was the solution.
Kind regards,
Gianni
P.S. I have worked on Ora 12.2...R2 up to two months ago...now we are on Ora 19c...
------------------------------
Gianni Sandigliano 
IT
------------------------------
                
Hi Anna
Which packing code are you using for the field in UnifAce?
And I did a quick look into the Uniface documentation about "Oracle Data Packing"
All date related fields are map to "date", no one of them to "timestamp"
@Gianni: is "date" the same as "timestamp" in Orcale?  
 [we only use MS products ("politically motivated") :-( ]
And as Gianni already wrote, try a reverse engineering, i.e. load the definitions from the ORACLE-table into a dummy model 
Ingo
Hi Anna
Which packing code are you using for the field in UnifAce?
And I did a quick look into the Uniface documentation about "Oracle Data Packing"
All date related fields are map to "date", no one of them to "timestamp"
@Gianni: is "date" the same as "timestamp" in Orcale?  
 [we only use MS products ("politically motivated") :-( ]
And as Gianni already wrote, try a reverse engineering, i.e. load the definitions from the ORACLE-table into a dummy model 
Ingo
Ciao Annalisa & Ingo,
Following Ingo question I've made a quick test... :-)
Oracle has two basic Data Types in this scenario:
- Date
- Timestamp
Any Oracle Date can contain either a date, a time or a datetime; Uniface is filling the missing part when needed.
Oracle Timestamp can contain a datetime with larger precision at ticks level.
Uniface packing support:
- Data Type: Date           Packing codes: D, D1-13 => Oracle Date
- Data Type: Datetime Packing codes: E, E1-E11 => Oracle Date
- Data Type: Time          Packing codes: T, T1-T4 => Oracle Date
- Data Type: Datetime Packing codes: E12 => Oracle Timestamp(6)
- Data Type: Datetime Packing codes: E13 => Oracle Timestamp(7)
- Data Type: Time          Packing codes: T5 => Oracle Timestamp(8)
- Data Type: Time          Packing codes: T6 => Oracle Timestamp(9)
- Data Type: Time          Packing codes: T7 => Oracle CLOB
Uniface documentation is NOT fully updated!!!
@Annalisa: you have 4 possible choices with an Oracle timestamp... my guess for your case is for one of these two:
- Data Type: Datetime Packing codes: E12 => Oracle Timestamp(6)
- Data Type: Datetime Packing codes: E13 => Oracle Timestamp(7)
Remember Uniface $datim on Windows is limited to 2 digits with ticks but if I remember well is more precise on other platforms.
Hope this helps...
Gianni
------------------------------
Gianni Sandigliano 
IT
------------------------------
                
Hi Anna
Which packing code are you using for the field in UnifAce?
And I did a quick look into the Uniface documentation about "Oracle Data Packing"
All date related fields are map to "date", no one of them to "timestamp"
@Gianni: is "date" the same as "timestamp" in Orcale?  
 [we only use MS products ("politically motivated") :-( ]
And as Gianni already wrote, try a reverse engineering, i.e. load the definitions from the ORACLE-table into a dummy model 
Ingo
Hi Anna
Very strange:-)
But glad you found a solution 
Ingo
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.