Just wondering where these files come from ?
I presume they may be related to a BLOB field somewhere ?

Can anyone tell me ? Or point me to the right topic in the
manual ? 4.21 b11

TIA

Dirk

Dirk Dinnewet wrote:
> Just wondering where these files come from ?
> I presume they may be related to a BLOB field somewhere ?

Tese are temporarily created tables. If you use SELECT ID FROM Customers,
DBISAM will create a temp table with these data - unless you define
RequestLiveResult = True or do a SELECT INTO "MEMORY\". See
TDBISAMSession.PrivateDir.

Ralf

Thank You

Dirk

"Ralf Mimoun" <nospam@rad-on.de> wrote in message
news:F935253C-DCE8-4530-9FA7-8A63614F7B9F@news.elevatesoft.com...
> Dirk Dinnewet wrote:
> > Just wondering where these files come from ?
> > I presume they may be related to a BLOB field somewhere ?
>
> Tese are temporarily created tables. If you use SELECT ID FROM Customers,
> DBISAM will create a temp table with these data - unless you define
> RequestLiveResult = True or do a SELECT INTO "MEMORY\". See
> TDBISAMSession.PrivateDir.
>
> Ralf
>
>
>

Dirk


To expand a bit on Ralf's comment. The temporary files created by DBISAM all have numeric file names. The extensions are the standard one's for DBISAM tables (dat = data, blb = blob = memo, idx = index). If they are still there after the application has closed then it probably indicates a problem of some sort since DBISAM should clean them up when the app closes. If they don't have a numeric file name then someone has specifically created them.

Roy Lambert

Thanks Roy (and Ralf).

Unfortunately these files reappear. There are indeed of the type numeric.dat
etc, size avg between
400 and 900 kB. I was wondering, do I need to set some option in the DB or
the session to
resolve this issue ?

Thank you.

Dirk


"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message
news:B2586576-6D89-42FA-8952-7B37BD1FAE53@news.elevatesoft.com...
> Dirk
>
>
> To expand a bit on Ralf's comment. The temporary files created by DBISAM
all have numeric file names. The extensions are the standard one's for
DBISAM tables (dat = data, blb = blob = memo, idx = index). If they are
still there after the application has closed then it probably indicates a
problem of some sort since DBISAM should clean them up when the app closes.
If they don't have a numeric file name then someone has specifically created
them.
>
> Roy Lambert
>

Dirk,

<< Unfortunately these files reappear.
 There are indeed of the type numeric.dat etc, size avg between
 400 and 900 kB. I was wondering, do I need to set some option
 in the DB or the session to resolve this issue ? >>

As Roy pointed out, DBISAM should automatically clean up these temporary files
whenever the application closes. The fact that these numeric file names are
not being deleted probably shows that your application is closing abnormally.
Can you perhaps add some logging to show the shutdown sequence, closing
of tables and so on?

Regards,
Dan

Dan,

I changed a couple of things :
- I set the temp dir in the session to a dir on my harddisk. This temp dir
  was left empty, and as per the manual, DBisam uses the application dir
  as temp dir. This might explain certain things. So far I haven't seen the
  files anymore.

About the shutdown, I do not immediatly have any trace, but this is what's
in my OnDestroy event of the datamodule. Is this well enough ?

Thanks

Dirk
====================================================

procedure TDM.DataModuleDestroy(Sender: TObject);
begin
DM.tblKwitantie.Close;
 DM.tblKlanten.Close;
 DM.tblPolisen.Close;
 DM.tblPolisDetails.Close;
 DM.tblPercentages.Close;
 DM.tblCompany.Close;
 DM.tblBetaalwijzen.Close;
 DM.tblBetalingen.Close;
 DM.tblPostCodes.Close;
 DM.tblRisico.Close;
end;

========================================================

"Dan Rootham" <roothamd@yahoo.co.uk> wrote in message
news:15A51C52-A92F-4F43-B748-D45CDEDD768D@news.elevatesoft.com...
> Dirk,
>
> << Unfortunately these files reappear.
>   There are indeed of the type numeric.dat etc, size avg between
>   400 and 900 kB. I was wondering, do I need to set some option
>   in the DB or the session to resolve this issue ? >>
>
> As Roy pointed out, DBISAM should automatically clean up these temporary
files
> whenever the application closes. The fact that these numeric file names
are
> not being deleted probably shows that your application is closing
abnormally.
> Can you perhaps add some logging to show the shutdown sequence, closing
> of tables and so on?
>
> Regards,
> Dan
>

Dirk


Now that I know these are indeed temporary files then they are created as Ralf said when you run a query that doesn't deliver a live result set. If they're not cleaned up automatically by DBSIAM then it does mean there's a bit of a problem with your code.

Reading the names in your TDM.DataModuleDestroy event I'm guessing that these are all DBISAMTables and hence will have nothing to do with the temporary files. You need to look at what you're doing with queries. My guess would be they're being left open somewhere.


Roy Lambert