At 05:07 AM 9/05/2005 +0000, you wrote:

>It's certainly a well written book. Thanks for that and I hope there
>will be a revision for 2.0.

There will be.

>I've read the section you pointed to and I don't see anything that
>seems to indicate that table names and field names must be uppercase,
>quite the contrary, they seem to be allowed (first line of quoted
>passage below).

Correct. Any combination you like. But unquoted identifiers are always
*stored* in uppercase.

>But, the tools I'm using seem to force upper case and
>I interpreted your msg as confirming my fear that uppercase was enforced?

"Enforced" in the sense that you don't have the option to store
case-sensitive identifiers unless you enclose them in double-quotes.

[..snip TFB quote..]
• In dialect 3, you can delimit "illegal" identifiers using pairs of

>double-quote
>symbols. Details follow.

It's the details that follow that explain how you can force the engine to
store case-sensitive identifiers (and make a rod for your back in so doing).

./hb