Re: Error Handling Coming Out of a Trigger

Del,

Your spot on! It's for a GL system. I am building a double entry GL system
for a healthcare system. I see what you mean about moving the code to the
procedures. It does make sense since the logic is executed on a user action
anyway, clicking the Save button. I guess my brain just sees it as an
action.

I agree that these things probably will become massive and very complicated.
I will speak with my boss about the idea of moving of it. Although for
clarity are you saying that you like to keep the logic in the front-end
Delphi app or keep the logic in stored procedures still sitting on the
back-end?

Also, regarding performance, I can't seem to find a way to handle to handle
my service lines on a transaction in a set based manner. Individual line
items can be discounted different amounts and may or may not be taxed. I was
thinking of using either a temp table and looping over it with a counter or
using a cursor on the small set of service lines that are owned by a
transaction. I need to process a write-off for each service line. Does
anyone have advice about my proposals? My first test is the temp table, I
was thinking that in larger client bases they could off-load the Temp db to
another physical disk for performance gain.

Thanks,

Brian Hollister

--
Got a big event coming up? Let us
help coordinate your event. For more
visit www.kissemgoodbye.com


.

Quantcast