On Tue, 12 Feb 2013 21:53:24 +0100, Thomas Steinmaurer
<ts@...> wrote:

>> We recently had database corruptions and had turned on forced write on
>> our databases on windows environment but we found that after we run our
>> client application gstat was no more showing the forced write status.

We

>> are using Delphi and IBO components but not sure what in the

application

>> is resetting this status. Has anyone come across this problem or know
>> what could be doing this.
>
> Yes. What IBO version are you using?
>
> AFAIR older IBO versions can switch the TIB_Connection.ForcedWrites
> property from dpbDefault to something else by accident, e.g. dpbFalse,
> when you double-click the TIB_Connection component to open the
> connection editor and switch to the characteristic tab (or even without
> that)
>
> Check out the ForcedWrites property before deploying the application.

The use of these dpb items is no longer possible for users other than
SYSDBA or owner in Firebird 2.5:
http://www.firebirdsql.org/file/documentation/release_notes/html/rlsnotes252.html#rnfb25-apiods-api-tighter

A very good reason to not use SYSDBA or owner for connecting to a database
for production work, I'd say.

Mark