This is described in Connecting to Excel.
When you sign onto an Excel file using AQT, you will be shown
The Excel ODBC Driver will assume that the first row in your worksheet / range contains your column names. If your column names are numeric, it will give it a name such as F1 instead.
If your worksheet name contains spaces, the ODBC driver can get confused and think that it is a range instead of a worksheet. This doesn't effect the way AQT operates.
When querying your data, you need to enclose Worksheet names in square brackets (this isn't needed for Ranges). If you wish to select a particular range of cells, you can include this as part of the table name. Examples:
ect * from Range1
select * from [Sheet1$]
select * from [Sheet1$A1:C10]
You can use AQT to update / insert / delete data in your Worksheets. By default, your Excel datasource will be read-only; if you try to amend amend data you will get message:
Operation must use an updateable query
The solution is to configure your ODBC Datasource to be non read-only (see Connecting to Excel for a description of this).
If you are using Excel frequently with AQT, you may wish to set up a number of named ranges in your Excel file. This is done as follows:
You should select a range that includes only your data. Do not select columns outside your data else you will get an error when trying to access the data.
Columns are maximum size of 255 bytes
Excel can sometimes truncate data at 255 bytes. This is a known issue with the Excel ODBC Driver that is described in http://support.microsoft.com/kb/189897/
There is a bug with Excel dates, that some AQT users have noticed while viewing Excel data in AQT, or while loading Excel data into a database.
Excel incorrectly thinks that 1900 was a leap year, and therefore that 29 Feb 1900 is a valid date (when it is not). This results in every day prior to and including 28 Feb 1900 being incorrect by one day. In other words, if an Excel spreadsheet shows a date as 10 Jan 1900, it will appear in AQT as 09 Jan 1900. If you load the date into your database, it will come across as 09 Jan 1900.
This is a problem with Excel, and there is little we can do about this.