recent ADO updates?

Gaetano@dbase.planet 1

I noticed that msado15.dll (32-bit!) carries a date of Jan 2021, could someone advise what changes were made to ADO? is it just bug fixes? or some new functionality?

Also, I am a dBase user and use sone large spreadsheet (100k lines) as inputs to a web app. I was trying to use ADO to connect to those Excel sheets snice MS has not released drivers for converting Excel to dBase or vice-versa on 64-bit platforms, but found that performance was dreadful. It takes 3 mins to scroll through those 100k records. Is this some issue with the dBase implementation of ADO or is it truly slow to work with Excel files through ADO?

Finally, the table names include the $ sign - e.g. Sheet1$ (which I interpret as being "the entire sheet1". It is a bit risky to be using special characters in table names. Is there a way around this?

Cheers,
Gaetano.

Erin Ding-MSFT 4,456 Reputation points

2021-03-25T01:29:32.037+00:00

@Gaetano@dbase.planet
Based on your description, your issue is more related to ADO, as tag "office-excel-itpro" focuses on general issues about Excel clients, I will remove it. Thanks for your understanding.
Daniel Zhang-MSFT 9,611 Reputation points

2021-03-25T07:06:10.043+00:00

Hi @Gaetano@dbase.planet ,
On improving the efficiency of ADO to process excel files, I suggest you can first read all excel into the recordset and then process.
And there are more suggestions in this thread you can refer to.
Best Regards,
Daniel Zhang
Gaetano@dbase.planet 1 Reputation point

2021-03-25T23:26:34.083+00:00

Thank you for your suggestions and links.

I do select all rows in a rowset and have tried to add a navigation to the last record then back to the first, but the timing is unchanged: 204 seconds for getting the 102,000 records into dBase.

I have meanwhile resorted to other methods: oleautomation to open the Excel file and save as CSV after changing the date format + RegExp+Windows API to read data from the clipboard + append the resulting CSV file in dBase, and although this sounds like a much longer path, it completes in less than 4 seconds for those 102k records...

It's a bummer that MS has no longer has a driver to export to dBase with Excel-64bit...