|
Subject:
|
Permanent Loops...
|
|
Posted By:
|
badeesh
|
Post Date:
|
9/12/2006 2:43:34 AM
|
I'm trying to code an application that sits and checks tables for new entries, and then generates a report that is mailed out based on the new entries. This would require the app to run permanently on the database server, and 'sniff' for want of a better word, the tables.
I'm having all these problems with connection timeouts, runtime errors and the lot and i'm convinced my concept/architecture/flow is incorrect.
My objects are being set to nothing, every one, I've checked. The app has a timer-controlled Sub-Routine which literally loops through the work required.
Can anyone recommend an architecture for setting up this sort of application?
that's how you make it go badeesh!
|
|
Reply By:
|
dparsons
|
Reply Date:
|
9/12/2006 7:10:25 AM
|
Why dont you place a trigger on the table and when data is inserted into the table, have the SQL Server send out the email?
"The one language all programmers understand is profanity."
|
|
Reply By:
|
BrianWren
|
Reply Date:
|
9/13/2006 4:50:10 PM
|
What is you database management system?
|
