Hello,

I have found the problem. I don't know how and why, but in the odbc-driver
was set the "No wait on locks"-checkbox. After I have removed the checkbox,
it works fine.

This was also the problem from yesterday with my triggers.

Thank you, I hope I can help some other user with the same mistake.


Regards.

Olaf Kluge







________________________________

Von: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] Im Auftrag von Anderson Farias
Gesendet: Montag, 20. Juli 2009 17:42
An: firebird-support@yahoogroups.com
Betreff: Re: [firebird-support]




Hi,

What's your trigger code? If you have something like :

if (new.field<>old.field) then
{...}

Be aware that if new.field or old.field is NULL than it will aways evaluate
to FALSE since null is not a value but a state (something like "unknown").
If that's the case then, test for nulls or, if using new FB versions, change

that to:

if (new.field is distinct from old.field) then
{...}

Regards,
Anderson Farias

----- Original Message -----
From: "Olaf Kluge" <olaf.kluge@... <mailto:olaf.kluge%40satron.de> >
To: <firebird-support@yahoogroups.com
<mailto:firebird-support%40yahoogroups.com> >
Sent: Monday, July 20, 2009 11:54 AM
Subject: [firebird-support]

> Hello,
>
> I have already a big problem. Thanks for your helping hand.
>
> If I change a value direct in my IB-Manager, the trigger of one table
> (after
> update) works fine. If I change the value over odbc (microsoft access),
> the
> value is changed, but the trigger doesn't works. I mean, if I change a
> value
> to null, the trigger works not over odbc, but only in one table not. If I
> change the value to another number, it works very well. Both inputs I have
> made in the linked table direct.
>
> If I change the value to null in my IB-Manager, the trigger works very
> well.
>
> The problem was never with the version 2.0 of firebird. Now I have version
> 2.1.1.
>
> Is this a bug? Should I update my firebird-installation=
>
> Thank you very much for your fast answer.
>
>
> Olaf Kluge
>
>
>
>





No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.392 / Virus Database: 270.13.20/2250 - Release Date: 07/20/09
06:16:00