>>I heard from someone or somewhere that you should not use select table.* and, instead should list all the fields.
>>
>>I'm about to it with select table1.*, table2.field1, table2.field2... where I do need all the fields from table1, about 27 of them.
>>Anyone have any input on this and if you should not do you have the reason?
>>
>>Thanks.
>
>No, there is nothing wrong with that statement IF you really need ALL fields from Table1, as Naomi already pointed.
>I prefer to use explicit list in my SQL commands. That makes my life easier If I need to add an aggregation function to that query I will now which fields I should use in GROUP BY clause.

Thanks to all for your input.
I should add that of the reasons for doing this is that some fields will probably be added and I don't want to have to track down what I forgot. This SQL feeds a sales order screen that I am still working on. The added fields will not be related to anything else.