I recently upgraded to DBISAM4 and I have just discovered that DBISAM
creates temporary tables (e.g. 37440.dat/37440.idx) during normal database
operation (nothing to do with ALTER TABLE etc.). The files are created in
the windows temp folder and they are never deleted, resulting in an endless
accumulation of these files, for which my application is responsible..

Is there any way I can controls where the files are placed so I can clean
when my application terminates.
The parameter Session.PrivateDir does not seem to have any affect on the
issue.

Norman Rorke
Desktop Financials Ltd

Norman

If the application ends normally then DBISAM will delete these temporary
files.
If they are still there, there is something different happening like power
down or application hang.

The parameter (property), Session.PrivateDir just will drive the path to
DBISAM save these temporary tables.

Eduardo

Norman,

> The parameter Session.PrivateDir does not seem to have any affect on the
> issue.

Could it be that your app does something to create the temporary tables
before your line of code that sets Session.PrivateDir?  For example, do
you have any queries open at design time?

--Bill Sparrow--


In article <5A4D8446-74B0-4A8B-AD55-5A4BB8BDD23E@news.elevatesoft.com>,
norman@desktopfinancials.com (Norman Rorke) wrote:

> *Subject:* DBISAM Temporary files
> *From:* "Norman Rorke" <norman@desktopfinancials.com>
> *Date:* Fri, 29 Dec 2006 20:04:58 +1300
>
> I recently upgraded to DBISAM4 and I have just discovered that DBISAM
> creates temporary tables (e.g. 37440.dat/37440.idx) during normal
> database
> operation (nothing to do with ALTER TABLE etc.). The files are created
> in
> the windows temp folder and they are never deleted, resulting in an
> endless
> accumulation of these files, for which my application is responsible..
>
> Is there any way I can controls where the files are placed so I can
> clean
> when my application terminates.
> The parameter Session.PrivateDir does not seem to have any affect on the
> issue.
>
> Norman Rorke
> Desktop Financials Ltd
>
>
>

Norman,

<<  I recently upgraded to DBISAM4 and I have just discovered that DBISAM
creates temporary tables (e.g. 37440.dat/37440.idx) during normal database
operation (nothing to do with ALTER TABLE etc.). >>

DBISAM has always done this.  Temporary tables are created for these
operations:

Table alteration
Table optimization
Canned result sets for SELECT queries

<< The files are created in the windows temp folder and they are never
deleted, resulting in an endless accumulation of these files, for which my
application is responsible.. >>

The only way that they don't get cleaned up automatically by DBISAM is if
the application is terminated improperly through the task manager (kill
task) or in the IDE (reset).

<< The parameter Session.PrivateDir does not seem to have any affect on the
issue. >>

As Bill pointed out, the only way that this would happen is if

a) you're executing queries prior to setting the PrivateDir property for the
session, or
b) you're actually using more than one session component and you're not
setting the property for the correct session, or all sessions

--
Tim Young
Elevate Software
www.elevatesoft.com

"Norman Rorke" <norman@desktopfinancials.com> wrote in
news:5A4D8446-74B0-4A8B-AD55-5A4BB8BDD23E@news.elevatesoft.com:

> Is there any way I can controls where the files are placed so I can
> clean when my application terminates.

Rather late, but one strategy to minimise this is to empty your Session's
PrivateDir in its OnStartup Event.

--
Chris
(XP-Pro + Delphi 7 Architect + DBISAM 4.24 Build 1)

Thank you Chris. The tip has been very handy.

Norman

"Chris Erdal" <chris@No-Spam-erdal.net> wrote in message
news:Xns98C06409D278014torcatis@64.65.248.118...
> "Norman Rorke" <norman@desktopfinancials.com> wrote in
> news:5A4D8446-74B0-4A8B-AD55-5A4BB8BDD23E@news.elevatesoft.com:
>
> > Is there any way I can controls where the files are placed so I can
> > clean when my application terminates.
>
> Rather late, but one strategy to minimise this is to empty your Session's
> PrivateDir in its OnStartup Event.
>
> --
> Chris
> (XP-Pro + Delphi 7 Architect + DBISAM 4.24 Build 1)
>