ODBC was conceived as a way of making it as easy to connect to a particular datasource such a relational database, text file, data document (e.g.
XML), web-based data or spreadsheet Currently, the state of the art in ODBC for Access and Excel is the Microsoft Access Database Engine 2010 Redistributable which can be downloaded here.
The next display shows a DSN connection for the Excel file above.
EOF row Count = row Count 1 If row Count = 1 Then Wscript. I strongly suggest that you try to find out why your earlier attempts to use Access were so unsatisfactory.
As a final comment I have to say that if you are doing something that takes "several seconds" to do in Excel but "takes around 20-25 min" to do in Access then I strongly suspect that you are using Access in a very inefficient way, but that's a topic for another question (if you care to pursue it). Execute "INSERT INTO [Sheet1$] (ID, Last Name, First Name) VALUES (11, 'Dumpty', 'Humpty')" con. Echo "Done." ..indeed append a new row in the Excel sheet with the data provided.
Of course you give a name to each column of the file too!
With ODBC, you can summarise, and select just the data you need, in an Excel workbook before importing it into SQL Server.
If you use the ODBC driver, then your Excel workbook becomes a little SQL-based relational database.