Q. How can I 'see' the number of table id's access is using for tracking
recordsets?
Details:
I have some ado code that itterates through a recordset and calls a
procedure on each record. This procedure calls a hierachy of other
subs/functions etc which _do_ instantiate several custom objects (class
modules), recordsets, both ado and dao at different times. Eventually the
code breaks with the error number -2147467259, (though has also been
broken with error number 3048 - I assume whether it breaks during an ADO
or DAO operation) and the message "Cannot open any more tables"
I believe (I've checked several times and am about to check again) that
every object (custom or access) is closed and set = nothing, so the
number of table id's at any given time shouldn't be extraordinary.
In theory, if everything is being closed and all garbage being collected,
I should be able to iterate through an infinite number of records and
execute this procedure, knowing that when the procedure finishes, things
are as they were when it started, but clearly they're not, and after about
250 records I get the error.
IF I can peek at some attibute of a recordset, or of the connection or of
something that gives me a hook into whats happening 'under the bonnet',
I can see when in the process the 'count' of table id's starts to climb,
I could then identify the problem.
any ideas?
Thx
Glenn