ODBC decimal format extent field in view

Posted by Richard.Kelters on 24-Feb-2017 05:27

I've created a view (using knowledgebase.progress.com/.../fileField ) on a table with a decimal extent field. The individual elements of the extent field get a point as decimal-point while other non extent decimal fields get a comma as decimal-point.

Is there a way to correct this?

Enviroment: Linux 11.5.1 database server, ODBC client Acces 2007 using 32-bit OE 11.5 driver

All Replies

Posted by Stefan Drissen on 24-Feb-2017 07:41

An example output of the sql script as created by that .p would help.

PDSOE auto-format is unable to make that .p automatically legible.

Posted by Richard.Kelters on 24-Feb-2017 08:53

An example of one table/view:

DROP VIEW sql92."CADVPR";

CREATE VIEW sql92."CADVPR"

(

"CUNR",

"PRNR",

"CASPR_1",

"CASPR_2",

"CASPR_3",

"CASPR_4",

"CASPR_5",

"CASPR_6",

"CATYPE",

"CASDAT",

"CAEDAT",

"CRNR"

)

AS SELECT

"CUNR",

"PRNR",

convert ('decimal', nullif( pro_element ("CASPR" ,1 ,1),'?') ) ,

convert ('decimal', nullif( pro_element ("CASPR" ,2 ,2),'?') ) ,

convert ('decimal', nullif( pro_element ("CASPR" ,3 ,3),'?') ) ,

convert ('decimal', nullif( pro_element ("CASPR" ,4 ,4),'?') ) ,

convert ('decimal', nullif( pro_element ("CASPR" ,5 ,5),'?') ) ,

convert ('decimal', nullif( pro_element ("CASPR" ,6 ,6),'?') ) ,

"CATYPE",

"CASDAT",

"CAEDAT",

"CRNR"

FROM pub."CADVPR";

Posted by marian.edu on 25-Feb-2017 01:02

Hi Richard,


is there any reason you don’t use the decimal field extent directly instead of the `old school` pro_element approach? That’s available since 10.A, you’re on 11.5 so just drop pro_element and change the select to something like this…

SELECT

"CUNR",
"PRNR",
“CASPR[1]",
“CASPR[2]”,
“CASPR[3]”…


Marian Edu

Acorn IT 
+40 740 036 212

Posted by Richard.Kelters on 25-Feb-2017 10:17

Clearly I'm a newby regarding ODBC, I'll give that a  try!

Posted by Richard.Kelters on 07-Mar-2017 06:48

I changed the views and they work fine, thanks Marian.

Unfortunately our customer still has the same problem in MS Acces. Apparently it seems to be an Acces issue because when I use SQL Squirrel or Libre Office I get consistent behavior. I don't have MS Acces.

This thread is closed