Hello All,

I'm working on a program written in Delphi 6 pro and DBISAM. Over time the source directory fills up with small files
of type DAT and IDX with names such as

17481.idx and 17481.dat

There is always a matching dat file for each idx file. The size of all the idx files is always 25088 bytes and the size of the
dat file is always 5888 bytes. The timestamps fo the files also always match.

I delete these files from time to time with no adverse effect but I do wonder where they come from
and what I might be doing to have them be created and remain in the directory.

I've tried to look at the file content with dbsys without success.

Can anyone give me an idea of where these files come from and what they are? I've attached a zip file with
a matched set.

Thanks to all.

oliver

These are temporary files created by DBISAM and correspond to queries in
your application - these usually represent canned result sets. The reason
they end up in your app folder is that your session temp path is probably
not set so it defaults to app folder.

DBISAM is supposed to get rid of these once it's done with them (meaning you
close the query in code) or at least when your app closes .

The main reason otherwise for these to be left behind  is if app is crashing
so dbisam never gets to clean up.

What version of dbisam are you using? If 4.28 then let's wait for Tim as i
noticed something similar.

If older version (4.27b5 or older) then check your app and make sure you're
closing everything properly (e.g. closing all query resultsets ; not using a
try/except block where exception skips closing the query, etc).

Raul


"Oliver" <dro@mettrix.com> wrote in message
news:E63DE86C-DC1F-488C-A3AE-E434F052B30B@news.elevatesoft.com...
> Hello All,
>
> I'm working on a program written in Delphi 6 pro and DBISAM. Over time the
> source directory fills up with small files
> of type DAT and IDX with names such as
>
> 17481.idx and 17481.dat
>
> There is always a matching dat file for each idx file. The size of all the
> idx files is always 25088 bytes and the size of the
> dat file is always 5888 bytes. The timestamps fo the files also always
> match.
>
> I delete these files from time to time with no adverse effect but I do
> wonder where they come from
> and what I might be doing to have them be created and remain in the
> directory.
>
> I've tried to look at the file content with dbsys without success.
>
> Can anyone give me an idea of where these files come from and what they
> are? I've attached a zip file with
> a matched set.
>
> Thanks to all.
>
> oliver
>
>
These are temporary files created by DBISAM and correspond to queries in
your application - these usually represent canned result sets. The reason
they end up in your app folder is that your session temp path is probably
not set so it defaults to app folder.

DBISAM is supposed to get rid of these once it's done with them (meaning you
close the query in code) or at least when your app closes .

The main reason otherwise for these to be left behind  is if app is crashing
so dbisam never gets to clean up.

What version of dbisam are you using? If 4.28 then let's wait for Tim as i
noticed something similar.

If older version (4.27b5 or older) then check your app and make sure you're
closing everything properly (e.g. closing all query resultsets ; not using a
try/except block where exception skips closing the query, etc).

Raul


"Oliver" <dro@mettrix.com> wrote in message
news:E63DE86C-DC1F-488C-A3AE-E434F052B30B@news.elevatesoft.com...
> Hello All,
>
> I'm working on a program written in Delphi 6 pro and DBISAM. Over time the
> source directory fills up with small files
> of type DAT and IDX with names such as
>
> 17481.idx and 17481.dat
>
> There is always a matching dat file for each idx file. The size of all the
> idx files is always 25088 bytes and the size of the
> dat file is always 5888 bytes. The timestamps fo the files also always
> match.
>
> I delete these files from time to time with no adverse effect but I do
> wonder where they come from
> and what I might be doing to have them be created and remain in the
> directory.
>
> I've tried to look at the file content with dbsys without success.
>
> Can anyone give me an idea of where these files come from and what they
> are? I've attached a zip file with
> a matched set.
>
> Thanks to all.
>
> oliver
>
> begin 0644 17481.zip
> M4$L#!!0````(`$:CMSH3,EQFJ0````!B```Y````4')O9W)A;2!&:6QE<R]"
> M;W)L86YD+T1E;'!H:38O4')O:F5C=',O5$535"!404(O,3<T.#$N:61X[=P]
> M:@)1%(#1-S/!N(R`5;('(03!!9C&?JSSHT)F"RFR(G$#-N(67,CH8*GD-@Z"
> M<PZ\YO)5CUO?/)WT?M=_TT&Y>1U^[?:K<ILUP_SXLM1A6>KX!_SO)4XB65'$
> M4;L>4I'J.NZX0X_C[X_EYUL5EQ<\QTFHR..F7<W^`P``````````````````
> M`````````%Q-?U+-G]YG/XLX/3>*DY#;R[?6Z0/_!U!+`P04````"`!&H[<Z
> MJ.SDKU`!````%P``.0```%!R;V=R86T@1FEL97,O0F]R;&%N9"]$96QP:&DV
> M+U!R;VIE8W1S+U1%4U0@5$%"+S$W-#@Q+F1A=.W8O4K#4!@&X#?_MI-"%5Q$
> MZ2`X]`($P29-)9"?8Y,.A4)`<@-.KA6<.GA%(C@+(IW<O0.OP*2U0S3A(V(\
> M#9QG2&AY#RWY7DY"9*SH\\?[23=Y/C^[7KP_)*]2]J6$O#?)R$[RU\=MX.[&
> M<.<?W2=P\_T_"I5(4"R'T3F>].R@`OM44"C1L<9A%'CV*#8#+^PY?A0SGUY6
> M7=LZG297V8],Z?`FD*%<1A,ZQ]-RT]T"#JB@4&(WW_]TXC&S1_2ZRAK7?P6:
> M9;*`]2.;#G.B9H?TH>.8"C;+L.^&_W31]_+]3^<]=FN8>*MY_5<A.ZRNN^$?
> MD7`('`$G9%(H)IY_RFA0O.$%G>-)P@RX!5PR*13;R?>_OHDWKO\ZM/1J,'^S
> M]__9LO\O9%(HUOG1?['_KQA0!W9HT4&.UOUGXEW?+[69'P_,7C;I]9E>5%4+
> M#>S_)U!+`0(4`!0````(`$:CMSH3,EQFJ0````!B```Y````````````(```
> M``````!0<F]G<F%M($9I;&5S+T)O<FQA;F0O1&5L<&AI-B]0<F]J96-T<R]4
> M15-4(%1!0B\Q-S0X,2YI9'A02P$"%``4````"`!&H[<ZJ.SDKU`!````%P``
> M.0```````````"```````0``4')O9W)A;2!&:6QE<R]";W)L86YD+T1E;'!H
> M:38O4')O:F5C=',O5$535"!404(O,3<T.#$N9&%T4$L%!@`````"``(`S@``
> *`*<"``````````
> end
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4139 (20090608) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>



__________ Information from ESET NOD32 Antivirus, version of virus signature database 4139 (20090608) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

Raul,

<< What version of dbisam are you using? If 4.28 then let's wait for Tim as
i noticed something similar. >>

You are correct - 4.28 has a bug whereby the temporary tables generated by
query result sets are not getting deleted properly.

A fix will be available in a Build 2 very shortly.

--
Tim Young
Elevate Software
www.elevatesoft.com