Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Using a trigger on an audit table may cause multiple ent
Message
 
To
26/02/2007 13:33:58
Mike Cole
Yellow Lab Technologies
Stanley, Iowa, United States
General information
Forum:
Microsoft SQL Server
Category:
Other
Environment versions
SQL Server:
SQL Server 2000
Miscellaneous
Thread ID:
01198853
Message ID:
01198877
Views:
10
>>By the way as soon as the user selects Save, the Save button is disabled so the problem is not due to users pressing Save multiple times. Does anyone have any suggestions?
>
>
>What happens when you manually change the fields outside of your application? I would think that would be the best way to tell whether this is related to your trigger/SQL Server, or to the application.
>
>Can you consistantly re-create the problem?

If I change the values of the QPR fields by doing an Update using the SQL Query Analyzer or external code, the Trigger does not fire thus the QPRAudit table has no record of the modification to the original record.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform