Hi Steve,

Thanks for writing back.

>Well, for me, I just find it a lot easier, and cleaner, and less prone to things getting hosed up by keeping all of my updateable views as SELECT * FROM table with no joins. Maybe I'm easily confused, but I just try to be clever where it provides the greatest yield, and applying the KISS principle liberally everywhere else *s*.
>

This all makes perfect sense except the part about you being easily confused. I think not!

>If you have highly normalized tables, using surrogate keys and stuff for the "codes" values, you can usually avoid having to include the "user-friendly" stuff simply by binding a combobox control to the FK field, and letting *it* display the "translation".
>

Would a Client/Server implementation effect the above idea, or would placing the lookup tables on the local drive negate any C/S issues?

>OTOH, if I'm pulling up a customer order and want to display the customer name and address, I'll just pull up the order record, and use the FK value to pull up a R/O parameterized view that allows me to display the name, adderess, etc.
>

I am leaning towards this idea for my current situation which is a C/S app.

Thanks again.

Kendall