> In the good old days identifiers were always UPPER_CASE and I prefer to
> retain that convention. Using lower case when writing scripts was
> possible, but keeping to the UPPER_CASE version made everything
> consistent, and as I remember dBase would use any valid UPPER_CASE
> character set as long as you did not try and mix them.
>
> People kept pestering for upper and lower case, and the "MiXeD" method
> seemed a way to go, but I never saw any strong reason that it was
> actually NECESSARY. It was pure aesthetics and of little practical value
> as no one in their right mind would use "UPPER" and "Upper" as two
> different fields (would they?).

C and Java folks might. They have been argueing for years that case
sensitivity is a good thing.

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server
Upscene Productions
http://www.upscene.com