masotti wrote:

> Hi Lester,
>
> Lester Caine wrote:
>> The only problem it turned out I had was that the problem updates were not
>> ACTUALLY wrapped with a transaction so were using the driver default one - which
>> is simply wrong.
>>
>> Adding a transaction wrap solved the problem ...
>
> I'm impressed! Seems that my first guess was really a good hint. Doesn't
> happen often.. :)

Well the real problem was I had ASSUMED that the default transaction had been
overridden ... when in fact there simply was not a transaction active other then
the driver default :(

It would be useful to change the driver so that it DOES use a more generic
default ...

--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php