Hi all,<br>
<br>
the database I designed is used to generate a tree view applet (see my Thread in the SQL Forum :-D). In order to prevent my prog from looping (due to cross references) I've tried a lot of solutions, the one i choosed is to create a clone of the tables used to create my tree.<br>
<br>
Before my routine, I create a clone, and after the creation of my tree (deletion of critical rows), I drop that clone.<br>
<br>
My problem is that the size of the database (an Ms Access one) is increasing ... (from 600Ko up to 32Mo after 10 operations).<br>
<br>
Lauching Ms Access and compacting the database is the worst solution, because it requires the intervention of the user.<br>
<br>
I'd like to know if there is a solution under Perl&DBI to execute such an operation so that it is totally transparent for the final user.<br>
<br>
Thanks.<br>
Thomas<br>
<br>
<br>
<br>
<br>
the database I designed is used to generate a tree view applet (see my Thread in the SQL Forum :-D). In order to prevent my prog from looping (due to cross references) I've tried a lot of solutions, the one i choosed is to create a clone of the tables used to create my tree.<br>
<br>
Before my routine, I create a clone, and after the creation of my tree (deletion of critical rows), I drop that clone.<br>
<br>
My problem is that the size of the database (an Ms Access one) is increasing ... (from 600Ko up to 32Mo after 10 operations).<br>
<br>
Lauching Ms Access and compacting the database is the worst solution, because it requires the intervention of the user.<br>
<br>
I'd like to know if there is a solution under Perl&DBI to execute such an operation so that it is totally transparent for the final user.<br>
<br>
Thanks.<br>
Thomas<br>
<br>
<br>
<br>