The whole idea of SQL is that you reference schema objects by names, and not by their PHYSICAL position. In the old punch card days, we did the sort of thing you want to do inside 3GL programming languages. The READ() statement would go to the start of the record, grab bytes, and put them into local variables int he order in which they PHYSICALLY appeared. That is why "READ(a,b,c)" is not the same as "READ(c,a,b)", but "SELECT a, b, c FROM Foobar;" is the same as "SELECT c, a, b FROM Foobar;".
Since officially the columns have no ordering within a row (just as the rows have no ordering in a table), what does the phrase "first six columns" mean? You need to learn to think in terms of LOGICAL models.
Yes, you can use the schema information tables to build a slow, meaningless query. But why do you want to do this?
Please post DDL, so that people do not have to guess what the keys, constraints, Declarative Referential Integrity, datatypes, etc. in your schema are.
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!