>Now that we're re-writing our application from scratch, I want to do the database design right. Currently, just about all of the tables contain the client ID plus the client name, and sometimes even the phone number.
>
>I know with normalization you should just have the client ID because the rest can be found in the clients table. But what do I do when I have that table in a grid and I need the name to show? Wherever the user is inputting stuff, s/he will want to know the name, not just the client number.
>
>I thought about using SQL to make a new temporary table that has the name from the clients table, and the rest from whatever table is being used. But then any changes will be made to the temp table. I don't want to have to do a seek on the regualr table to find the corresponding record everytime a value is changed!
>
>I'd like to avoid duplication the info, because now if the name or phone number changes, I have to search through all the tables and change all the occurances. But I also don't want to lose the ability to edit the table directly.
>
>Any suggestions?

If do not want to go with VIEWS, you can drop two object of the same source table in the Data Environment, use the first one for Data Manipulation and the other one for lookup table or whatsoever. You can have many object of the same table in the DE.