Re: Error Handling Coming Out of a Trigger

Brian,

It sounds like you are doing a GL or full accounting system. My experience
is that when you put those rules in the DB, the user usually has a
continuous stream of "new" rules that either they didnt describe in the
beginning or that arise as business changes. What usually happens is that
the triggers get so convoluted that they become unmaintainable , escpecially
if you have 3 or 4 programmers working on them over a period of a few years.
I would put the logic in the stored proc that you are calling to actually
update the data (the one firing the trigger). Triggers IMHO are for actions,
not edits. I acutally prefer to put the logic in the program and then they
can **never** come up with something that I cant handle in a straight
forward manner.

I think you are on the right track for the long hall.

Del


.

Relevant Pages

  • Write conflict error after adding trigger to table
    ... I have inherited an Access adp that directly connects to SQL Server. ... that database. ... stored proc in the database window instead of through the form, ... is preventing me from rolling these triggers to production where other apps ...
    (microsoft.public.access.adp.sqlserver)
  • RE: passing table to store proc
    ... There is no real way to pass tables to a stored proc. ... triggers would be much smaller, ... with that, is that multiple triggers inserting into the same table, and ... > to pass the inserted and deleted table to store procedure, ...
    (microsoft.public.sqlserver.programming)