Our employees use a small dbisam based company phonebook/dialer application
(D7, Dbisam 4). Access from server via mapped network drive, no C/S, max. 50
read-only users run the app in parallel.

Sometimes (seems to be random, independent of the number of users) the app
does not start due to the engine error above. It seems, the server (Win2K)
doesn't allow to access the table file. Users access rights are not the
problem.

Any idea where to look for the cause of the error (even it may be no dbisam
problem itself)?

Thanks
Uwe

Uwe


Have you tried repairing the table/tables?

Roy Lambert

> Have you tried repairing the table/tables?
> Roy Lambert

I may try this, but the error occurs arbitrary and some time later or from
other workstation
it works fine without repair/reindex or other manual activities.

I should note, we run all user "clients" on two CITRIX-Metaframe-Servers.
The application and DB  is located on another Win2k-Server.

Uwe

Uwe,

<< Sometimes (seems to be random, independent of the number of users) the
app does not start due to the engine error above. It seems, the server
(Win2K) doesn't allow to access the table file. Users access rights are not
the problem. >>

So, the table is never actually updated by any of the users ?  If so, then
corruption can be ruled out completely, and that just leaves an OS-related
error.   Have any other applications ran into problems with reading files
from the server machine ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

> So, the table is never actually updated by any of the users ?

Rarely and I found no correlation of updating and the orrcurence of this
error.

> Have any other applications ran into problems with reading files from the
server
> machine ?

We had no such complaints for other files. Nevertheless I think I have to
look for OS related reason: The database file could not be opened/read in
case of this error by any other file reader too - so it is no corruption /
file contents problem. (We never encountered any db corruption after
switching from paradox to dbisam, Tim

Uwe

Uwe,

<< We had no such complaints for other files. Nevertheless I think I have to
look for OS related reason: The database file could not be opened/read in
case of this error by any other file reader too - so it is no corruption /
file contents problem. (We never encountered any db corruption after
switching from paradox to dbisam, Tim>>

I would certainly investigate possible network problems.  It could simply be
that the network read is failing due to an error.  BTW, you can use the
EDBISAMEngineError.OSErrorCode property to find out the exact OS error that
is causing the read error, but you have to trap it in your application via
an exception handler right after the operation that causes the error:

http://www.elevatesoft.com/dbisam4d5_edbisamengineerror_oserrorcode.htm

--
Tim Young
Elevate Software
www.elevatesoft.com