>>You might be bettor off putting the keywords in a one-field table so you can add to it. NUMBER, SUM, COUNT, etc., are also bad for field names.
>
>They are not too bad as long as table aliases are using in conjunction with field names, i.e. accurate coding is even more important.

This works except when I had to use it in a UNION. Oracle refused to run a query with a field named NUMBER -- even with the table alias attached to it. Actually it was an Oracle view of a DB2 table. The DB2 table had a field named NUMBER. So we redefined the Oracle view with a SELECT NUMBER as "PWSID" ... to overcome the problem.