My app handles several queries which are generated on user demand in order to support easy
data input. Also queries are used for reports and ...
I strictly close all queries before exit app, but I still get some "number-named" temp
tables ".dat", after I close app. It is also odd that these "temp files" can not be opened
by dbsys.
Please, advise

Andrej,

What DBISAM version you are using ?
Also, are you using Client/Server? What OS?

--
Fernando Dias
[Team Elevate]

Sorry, i use D6 and dbISAM ver.4.25

"Fernando Dias" wrote:

Andrej,

What DBISAM version you are using ?
Also, are you using Client/Server? What OS?

--
Fernando Dias
[Team Elevate]

Andrej

Yoiu didn't say if you are using Client/server or what OS...
If you are using C/S, it can be a permissions problem: temporary file are
being created by the server using the "system" account and you are trying to
open them directly using DbSys using your user account... This is only a
guess, of course.

--
Fernando Dias
[Team Elevate]

No, I do not use C/S. Pure desktop app.
"Fernando Dias" wrote:

Andrej

Yoiu didn't say if you are using Client/server or what OS...
If you are using C/S, it can be a permissions problem: temporary file are
being created by the server using the "system" account and you are trying to
open them directly using DbSys using your user account... This is only a
guess, of course.

--
Fernando Dias
[Team Elevate]

andrej


Is is just the .dat files or are there .idx and .blb files as well? I ask because .dat is a common extension and you may have them created by another app.

DBISAM only leaves the temporary tables lying around if there has been an error in the app so another question is does the app finish cleanly or not and are any of these queries wrapped in try except blocks which aren't handled properly?

Roy Lambert [Team Elevate]

And I am able to delete those temp files, just can not open. And since I exit my app,
there is no reason to be locked.

andrej wrote:

No, I do not use C/S. Pure desktop app.
"Fernando Dias" wrote:

Andrej

Yoiu didn't say if you are using Client/server or what OS...
If you are using C/S, it can be a permissions problem: temporary file are
being created by the server using the "system" account and you are trying to
open them directly using DbSys using your user account... This is only a
guess, of course.

--
Fernando Dias
[Team Elevate]

yes, there are also .idx files with same names as .dat. Did not find any blb, but I do not
use much .blb.
So, I am pretty sure these files are produced by my app. And I am sure, I close all
queries before closing app. But I do not have them wrapped in try exept blocks, ecxept
maybe in few occasions. Does it matter? App is on local PC and does not have to work on
network.

I delete those files from time to time but it is no "clean".

a
Roy Lambert wrote:



andrej


Is is just the .dat files or are there .idx and .blb files as well? I ask because .dat is
a common extension and you may have them created by another app.

DBISAM only leaves the temporary tables lying around if there has been an error in the app
so another question is does the app finish cleanly or not and are any of these queries
wrapped in try except blocks which aren't handled properly?

Roy Lambert [Team Elevate]

andrej


>yes, there are also .idx files with same names as .dat. Did not find any blb, but I do not
>use much .blb.

OK so that pretty much guarantees that they are left over tables.

>So, I am pretty sure these files are produced by my app. And I am sure, I close all
>queries before closing app. But I do not have them wrapped in try exept blocks, ecxept
>maybe in few occasions. Does it matter? App is on local PC and does not have to work on
>network.

DBISAM is meant to clean them up when its finished with them. The normal reason they get left over is an app crashing. They won't do any damage but it is a good indication that there is a problem somewhere that needs fixing.

Roy Lambert [Team Elevate]

ok, can you give an example, since appdo not crash "visually". I use lots of "combobox"
and I fill them "querries", but all of them are closed before exiting. But them may be
left open inbetween (alfer filling until next fill).
Roy Lambert wrote:

andrej


>yes, there are also .idx files with same names as .dat. Did not find any blb, but I do not
>use much .blb.

OK so that pretty much guarantees that they are left over tables.

>So, I am pretty sure these files are produced by my app. And I am sure, I close all
>queries before closing app. But I do not have them wrapped in try exept blocks, ecxept
>maybe in few occasions. Does it matter? App is on local PC and does not have to work on
>network.

DBISAM is meant to clean them up when its finished with them. The normal reason they get
left over is an app crashing. They won't do any damage but it is a good indication that
there is a problem somewhere that needs fixing.

Roy Lambert [Team Elevate]