For some reason, the Sequence Manager was having a problem with using AutoCommit with MsAccess. I went and made sure all my stores and deletes had transacations around them. I then went into the ojb.properties and turned the useAutoCommit to 2 (aka false) and ignoreAutoCommitExceptions to true. This seemed to fix my SequenceManager problem as it no longer tries to use the autocommit feature.
Graham -----Original Message----- From: Graham Lounder [mailto:[EMAIL PROTECTED]] Sent: September 4, 2002 8:16 AM To: OJB Users List Subject: AutoCommit Questions Hi all, I'm having some problems with the autoincrement feature of OJB 0.9.5. The app will start off fine, but once in a while, when the SequenceManager needs a new set of keys, it blows up for some reason. The first error is that it can not set the AutoCommit to false. I'm using MsAccess so normally this exception is not displayed. After this, the SequenceManager complains that it can't autoincrement the class. I noticed that there were some options for AutoCommit in the properties file. Can I turn this feature off? Also I'm not using transactions as MsAccess does not support them. If anyone has any information on this I would be greatly appreciative. Thanks in advance, Graham ============================================ Graham Lounder Java Developer Spatial Components Division CARIS 264 Rookwood Ave Fredericton NB E3B-2M2 Office 506 462-4218 Fax 506 459-3849 [EMAIL PROTECTED] http://www.spatialcomponents.com ============================================ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
