ok.

the reason for doing this was a whim of my boss. He wanted to fields to be
easy to read. I'm going to try ton convince him it's just not worth the
effort.

Thanks!

On 9/21/06, Thomas Kellerer <IJFQSFTGESJU@...> wrote:
>
> No, there is no way to avoid this. As soon as you use double quotes
> with an identifier, the whole thing gets case sensitive. Now when you
> create columns with double quotes, they are stored "as is", that is
> case matters. The only way to supply the correct name later in the
> SELECT is to use double quotes again (otherwise it's case-insesitive)
>
> This is standard ANSI SQL behaviour, and basically all the DBMS I know
> and work with, behave that way.
>
> That's one of the reasons I never ever use double quotes. If you use
> them, it's asking for trouble (which you just found out)
>
> Why do you create the table with double quotes in the first place????
>
> Thomas
>
> --- In firebird-support@yahoogroups.com<firebird-support%40yahoogroups.com>,
> "Fernando Salaices"
> <fsalaices@...> wrote:
> >
> > Hello.
> >
> > I'm having some trouble with double quotes: how can I get Firebird to
> > recognize fields in a SELECT statement in UPPERCASE even if the
> fields in
> > the CREATE TABLE statement were created using "DoubleQuotes"? It
> seems that
> > if you use double quotes to create the table you must use them to select
> > them also, but is there any way to work around this situation with out
> > having to recreate the tables with out double quotes?
> >
> > thanks!
>
>
>



--

Saludos,
Fernando Salaices.


[Non-text portions of this message have been removed]