At 05:07 AM 4/11/2003 +0000, you wrote:

>Hi helen
>
>sorry for bothering you so much. With the trigger you have re wrote
>for me could that make a difference from my original trigger?

Slightly. It will "do nothing" if the record isn't found to
update; otherwise it will always "do something".

>as of now the only possible problem we knew is that any null value
>could make a expression equal to null. But from my scenario I dont
>think I am getting a null value after all. because in table b, records
>can't be save if there is no value in requestqty.

Well, the only thing that comes to mind is that the record that you
*thought* was there wasn't there at all. If another transaction has
created that record, but hasn't committed it at the time the trigger fires,
then the trigger won't find it.

That's my last posting on this subject. I suggested before that you look
at what else is happening. All this guesswork is too time-consuming.

heLen