Leaderboard

I have been working with this ADO.AU3 UDF for more than a year. At the time of writing this, I am using beta 2.1.15. ADO in general allows connection to various data sources. The full documentation is available from Microsoft and a simple Google search will reveal the scope. This ADO UDF is very powerful and incorporates ideas from various other UDFs available on the Forums, such as the SQL UDF and others. The ADO UDF provides for an ADO connection using COM objects. The design is such that little knowledge of either ADO or COM is required. Combining ADO with AutoIt creates a very powerful package. The way this UDF is implemented it is not necessary to have deep ADO knowledge in order to connect and perform tasks. Since it uses ADO, in order to implement, the following is required a data source (such as a database) ODBC DNS driver and entry in the Windows Control Panel this ADO UDF #include of ADO.au3 in the user script Note that the examples should work by default. Note the connection values in each example. I have personally tested the ADO UDF on PostgreSQL databases, both locally and online, DBFs both locally and remote and briefly tested connectivity to other data sources. It all works as expected. I do not use the power of ADO to the full extent, as my needs are limited to basic reporting. The advantage is that standard SQL queries can be run over ADO to the data source - even to DBF files! The most important changes in this version 2.1.15 beta are as described below. The COM error handling makes provision for standard SQL blank result sets. This means that COM errors such as no-connection, faulty queries etc will result in a crash. Valid SQL with valid SQL responses can be processed in a manner which does not lead to a crash, but processed as a normal result. At the same time, a different implementation of the same UDF (this means you write your own part of the AutoIt code differently) means that such a blank result set may represent a blank ADO cursor, which must result in an ADO / COM error. The advantage is that a single UDF can now be implemented in different scenario's, on various data sources, with different error handling processes. I recommend this ADO.AU3 UDF to anyone wishing to connect to any external data source. Skysnake