>
>Might be, I don't know. I'm highly comfortable in doing this. It ensures that every field in the database is unique, which has it advantages in writing SQL commands with joins, but also in SQL results (like in views) in inmediately recognizing which table a field comes from. It also has a big advantage if you write an export program (like a mailmerge) where the user can pick its fields to export, so you avoid having to fiels (e.g. Name in patients table and Name in doctors table) to be the same.
>

Just do you don't misunderstand. There is no problem with naming fields the way you do. It's personal preference.