Hi,
I was browsing this thread: thread701-1163790 and I noticed a comment about the ordering of fields in a table not being relevant in a relational database.
Since the thread is closed I'd like to bring this topic up for debate. I can think of a situation in which the ordering of fields in a table is very relevant.
Suppose you have built in VBA code to query a table and send the result to an excel file. The query uses something like
The excel file now contains the columns from the table - in the order of the fields as they are defined in the table. Suppose that you also use Automation to modify the column formats in the excel spreadsheet so that they look nicer (maybe dates need re-formatting or the size of the columns need adjusting or the column headers need renaming). If the fields in the table are ever reordered, then the columns in the excel file will be "out of whack" with the formatting done by the built in VBA code.
Obviously changing the SQL to select each field one by one from the table instead of using the * would eliminate this potential problem.
Cheers...Ed
I was browsing this thread: thread701-1163790 and I noticed a comment about the ordering of fields in a table not being relevant in a relational database.
Since the thread is closed I'd like to bring this topic up for debate. I can think of a situation in which the ordering of fields in a table is very relevant.
Suppose you have built in VBA code to query a table and send the result to an excel file. The query uses something like
Code:
SELECT * FROM tableA
Obviously changing the SQL to select each field one by one from the table instead of using the * would eliminate this potential problem.
Cheers...Ed