I have an application running on a network with a data folder containing
the DBISAM database tables... The other PC's can make edits to those
tables no problem, BUT anywhere a TRANSACTION is used an ERROR 11013
occurs at the point when the transaction is COMMTTED.

I don't have this problem on my network, but my client does and the
tech's there have told me they checked the privelages to the TMP and
TEMP variables as well as turning off the anti-virus software.

Does anyone have any ideas I can try? I have read through similar posts
and we have tried what solved those issues but it doesn't appear to fix it.

Thanks,

Phil

Hey sorry, to be more specific I have nailed it down to the moment when
the transaction is started...
CaretakerDatabase->StartTransaction(0);

Thanks!

Phil.

Phil,

<< Hey sorry, to be more specific I have nailed it down to the moment when
the transaction is started...
CaretakerDatabase->StartTransaction(0); >>

Are you using any tables exclusively in your application ?  Also, what is
the TDBISAMSession's PrivateDir property set to ?  If it is set to the same
as the database directory, then you could have issues with DBISAM trying to
start a transaction on a temporary table that is already opened exclusively
by another user.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

I'm using queries in my transaction and I have set nothing to Exclusive
that I'm aware of. Also I have not manually set the PrivateDir property.

Does that help? And why would it work on my LAN network and not on my
clients? Maybe the tech's have not checked everything.

Thanks.

Phil,

<< I'm using queries in my transaction and I have set nothing to Exclusive
that I'm aware of. Also I have not manually set the PrivateDir property.

Does that help? And why would it work on my LAN network and not on my
clients? Maybe the tech's have not checked everything. >>

Do any of your queries generate canned (non-live) result sets ?  If so, then
yes, it could still be an AV software issue.  However, such an issue would
not occur during a StartTransaction, but rather when the query is executed.

You should definitely make sure that your PrivateDir for the TDBISAMSession
component is set to a local temporary files directory.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

Thanks for your comments... I went back to the tech's and got 'em to
check access to the programs folder where the EXE resides and magically
the client tells me it's all working now. (Never rely on another person
telling you something on the phone, especially when they say they don't
have much time).

I also added a feature to allow the user to select a private directory
if the default location is causing them problems, so I should have those
problems covered in the future.

Thanks again!

Phil.

Phil,

<< Thanks for your comments... I went back to the tech's and got 'em to
check access to the programs folder where the EXE resides and magically the
client tells me it's all working now. (Never rely on another person telling
you something on the phone, especially when they say they don't have much
time). >>



<< I also added a feature to allow the user to select a private directory if
the default location is causing them problems, so I should have those
problems covered in the future. >>

Yep, that should give you some additional safety.

I'm glad you got things resolved.

--
Tim Young
Elevate Software
www.elevatesoft.com