[vb6] Project Scanner

[LaVolpe]

Hi LaVolpe, use Seek method instead, it is much faster (100 times faster or more).
If it is still not fast enough, then consider to switch to DAO.

Thanx for the thought. But if MSDN documentation is correct, this will not be an option as it requires server-side cursor where a disconnected recordset (no DB) is used in this project. A client-side cursor is required for disconnected recordsets.

Seek: This method is supported only with server-side cursors. Seek is not supported when the Recordset object's CursorLocation property value is adUseClient.

[Eduardo-]

Thanx for the thought. But if MSDN documentation is correct, this will not be an option as it requires server-side cursor where a disconnected recordset (no DB) is used in this project. A client-side cursor is required for disconnected recordsets.

Ah. Then I would consider creating a temporary database file. It is not a lie that Seek is extremely faster.

[LaVolpe]

Ah. Then I would consider creating a temporary database file. It is not a lie that Seek is extremely faster.

Already tried that. The overhead of inserting records into the DB was significantly slower than using the disconnected RS. A sample project took over 2 seconds vs just 1/2 second for a RS. And yes, I used SQL Insert to add records, not the recordset.AddNew method.

P.S. I did get a PM from dreamManor. The main speed issue is parsing the procedures in his case. When he skipped that part of the process, the time needed was about 1/2. However, that was just to find where the main speed hit was occurring. I do have a faster routine to get through the procedures for the initial scan, but haven't offered that up yet. I will shortly and ask dreamManor to be kind enough to run that one for me. It's not ready yet though.

[Eduardo-]

My experience is that adding an index does not cause much overhead, and if the index is the primary key then the index is already there.
But I use DAO, I don't know with ADO.