[Note: This is a similar question as this one relating to LOAD TABLE and OPENSTRING. However, while I generally agree with the answers there, I feel there are different requirements for a primarily GUI-based solution within DBISQL.]
I just have to import an Excel file into my SA 11.0.1 database. It's a one-time operation, and it's a typical data file with the first line consisting of the column names. So I would like to minimize my efforts...
As I would like to automatically create the table (the worksheet contains lots of columns), I do not want to use LAOD TABLE. Instead I'm trying to use the DBISQL import.
So I have converted the excel file to a tab-delimited text file and tried to import. As the SA 11 DBISQL doesn't handle the first line differently, it seems inappropriate. (E.g. I can't even choose an integer type for any column because the column names in the first line all contain letters.)
So I switched to the SA 12 DBISQL, and luckily, it has the option to skip the first (n) lines. A senseful enhancement, thanks! So I felt the GUI is handling my simple task quite well, and I can now choose appropriate column types. (And it's nice that DBISQL v12 runs against a v11 server...)
But now I would like to use the first line to choose the column names (as can be done when importing text files within Excel, for example).
And that option seems missing, if I have not overseen anything...
Therefore I would suggest to add an "Interpret first line as column names" option in the GUI (and possibly in the INPUT statement).
I know, I can define an ODBC DSN for the data file and import from that (as suggested for the cited question), but I guess that's way too complicated for a GUI-based solution (and possibly a hurdle for a bunch of DBISQL users, too).