2010/4/23 Merlin Moncure :
>
> There's way too much logic going on there for me to test all the
> different cases.
>
> I suspect this is your problem: you triggered a case somehow which is
> not handled properly via your labyrinth of switches and loops. I
> highly doubt this is a case of database
2010/4/23 சிவகுமார் மா :
> 2010/4/23 Merlin Moncure :
>>
>> You haven't given enough information to make any sort of reasonable
>> diagnosis. Most people are going to assume the problem is on your end
>> but it's possible to know for sure without having the trigger function
>> at the very least.
>
2010/4/23 Merlin Moncure :
>
> You haven't given enough information to make any sort of reasonable
> diagnosis. Most people are going to assume the problem is on your end
> but it's possible to know for sure without having the trigger function
> at the very least.
>
Thanks merlin for the reply. T
2010/4/23 சிவகுமார் மா :
> 1. We have a production system tracking value added to a batch through
> series of stages. Value table is updated through triggers on data
> tables.
>
> 2. These trigger functions have been tested and validated for over 1.5
> years with more than 100,000 records.
>
> 3.
1. We have a production system tracking value added to a batch through
series of stages. Value table is updated through triggers on data
tables.
2. These trigger functions have been tested and validated for over 1.5
years with more than 100,000 records.
3. We found a difference in the calculatio
