Subject | BDE Emulation numbering issue with un-named columns |
---|---|
Author | Randal W. Carpenter |
Post date | 2007-06-27T19:30:16Z |
Hi All,
You probably already know this, but I just found an issue with un-named columns
(like the ones created with this query:
SELECT CUST_NO, COMPANY, (CITY||', ')|| STATE FROM CUSTOMER Customer
Note that in the BDE, it would name that one COLUMN3, in the IBO emulation it
will name it COLUMN2.
After a little investigation, it seems bde starts with 1 numbering columns,
whereas the ibo emulation of bde starts at 0...surely this has came up before
now :).
Where I find these I correct them by just naming the column using an AS clause
and using the name...but it sure would be nice if there was a way to avoid
going though every query (one of my programs has 180 queries pointing to
reports). Since I dont always add fields to the query list unless I plan to
directly access them (no need in reports, etc), they do NOT show up in a search
for the word COLUMN in my ide :(.
Any idea how to fix this easily?
thanks
Randal
You probably already know this, but I just found an issue with un-named columns
(like the ones created with this query:
SELECT CUST_NO, COMPANY, (CITY||', ')|| STATE FROM CUSTOMER Customer
Note that in the BDE, it would name that one COLUMN3, in the IBO emulation it
will name it COLUMN2.
After a little investigation, it seems bde starts with 1 numbering columns,
whereas the ibo emulation of bde starts at 0...surely this has came up before
now :).
Where I find these I correct them by just naming the column using an AS clause
and using the name...but it sure would be nice if there was a way to avoid
going though every query (one of my programs has 180 queries pointing to
reports). Since I dont always add fields to the query list unless I plan to
directly access them (no need in reports, etc), they do NOT show up in a search
for the word COLUMN in my ide :(.
Any idea how to fix this easily?
thanks
Randal