<Snip>

> I once had a customer who had TIB_Connection.ForcedWrites set to
> dpbFalse by accident (e.g. when it is set to dpbDefault and you are
> doing a double-click on it, again, by accident, because you wanted

to

> double-click the GeneratorLinks property, it changes to dpbFalse)

and he

> did wonder, why his database was always running in forced writes =

OFF,

> even after setting it to ON with gfix. ;-)
>
> Any chance this does apply to your situation as well?
>
>
> --
> Best Regards,
> Thomas Steinmaurer
> LogManager Series - Logging/Auditing Suites supporting
> InterBase, Firebird, Advantage Database, MS SQL Server and
> NexusDB V2
> Upscene Productions
> http://www.upscene.com
> My blog:
> http://blog.upscene.com/thomas/
>

No, I finally found the "culprit". Another programmer read a page on
the Firebird site stating how by setting that value to 1 increased
performance in some particular operation and he "ninja" applied the
change everywhere. For some reason, the 2.0 engine would still work
well (maybe it performs a "sanity check" ignoring nonsensical low
values below a thresold?) but the 2.1.1 engine would show the
drastical effects at full.