Subject | Re: [IBO] TIB_Query.Fields[I].FieldName returns quotes |
---|---|
Author | Helen Borrie |
Post date | 2003-09-03T00:24:45Z |
At 08:58 PM 2/09/2003 +0000, you wrote:
If you choose to define database objects with quoted identifiers, then you
are stuck with using both the dblquotes *and* case-sensitivity for
everything you do with those objects. The columns MYCOL and "MyCol" are
*different* column names, whereas MYCOL and MyCol are the same column name.
The tool (or strategy) you used for your Paradox-to-FB conversion allowed
you to have an illegal table identifier (FB object identifiers can't start
with a number) by double-quoting the identifier. It's a hack and any hack
has a cost.
Helen
>This may be a FB question, or an IBO question, I don't know. MyIt's a FB question which I've answered at least once for you in other contexts.
>apologies for asking here if it is infact an FB question.
>I am migrating from Paradox (BDE) to IBO, and am facing a few smallNo.
>issues on the way. The one at hand: I used field names that started
>with numbers in Pdx, such as '401kInfo' (retirement contributions in
>401(k) plans). But when I use 'ibquery.Fields[index].FieldName' the
>result includes quotes (viz '"401kInfo"')--which I don't want--I just
>want the name without the quotes. Is there anyway to set this up this
>way?
If you choose to define database objects with quoted identifiers, then you
are stuck with using both the dblquotes *and* case-sensitivity for
everything you do with those objects. The columns MYCOL and "MyCol" are
*different* column names, whereas MYCOL and MyCol are the same column name.
The tool (or strategy) you used for your Paradox-to-FB conversion allowed
you to have an illegal table identifier (FB object identifiers can't start
with a number) by double-quoting the identifier. It's a hack and any hack
has a cost.
>If not, is there a different way of setting it up, or someOnly if you redo your database with legal identifiers.
>standard convention (e.g. change the '4' to a 'Four').
Helen