🚀 go-pugleaf

Romain Strieff [TeamB] wrote in message ...
>In article <6ol4tl$8lm9@forums.borland.com>, CNeumann@Physix.com
>grudgingly admits...
>> When it is first selected, I do a LIST STAT and I see 3 seperate selects.
>> When I do a USE IN MYTABLE, it removes 1 and keeps the other 2.  When I
run
>> the routine again, I have 4 left after it is done.  I use VdB tables & MS
>> SQL tables.  I use the following scenario:
>>
>> **using VdB tables
>> set database to MYSQLTABLES
>> **using SQL tables
>> set database to
>> **using VdB tables
>> (etc.)
>>
>> If I just use the SQL routine, there is no problem.  If I just use the
VdB
>> routine, there is no problem.  When I use the above scenario to get the
use
>> of ALL of my tables (VdB & SQL), I have the problem.
>>
>Which problem?


When using BOTH, VdB & SQL tables at the same time, the problem occurs.

>If you:
>for n=1 to 50
>  use mtable in select()
>next
>you'll have the same table opened 50 times, what else did you expect?


I would expect 50 select's of MTABLE!  If I use the code that only accesses
VdB tables, the problem does NOT occur.  If I use the code that only
accesses the SQL tables, the problem does NOT occur.  If I instanciate the
VdB tables and later in the program select an SQL table, THE PROBLEM OCCURS!

>Or do I miss something?


DOH!

>If you you want to start afresh, just CLOSE DATABASES before opening any
tables.

All VdB tables are instanciated on initial execution.  SQL tables are
opened/closed as needed, primarily due to a VdB limitation of ONLY 1 SQL
table open at a time, whether or not opened as an alias.