AJ,

This is a good idea but I am not sure it belongs in the app itself (I leave that to others to decide)..  The way I do it now is I have all zip's blocked and I have a stored procedure that then marks them to deliver if they have aged 12 hours.  I have informed our customers of this delay and I have given them a work-around if this becomes an issue for them.  This saved my bacon with the new variant of bagle.

Dan S

Roberto & all,

I am actually just recently learning the extreme power of stored procedures.  It has been a bit of a learning curve but I feel that I can off-load most of my db clean up and strange customer requirements to the SQL server itself.  I have had no feedback as to weather or not this was the indended function of the stored procedures but they seem to be a very powerfull tool.  Just one example is that I let SpamFilter expire messages after 14 days.  However, some customers get so much garbage that they feel 14 day is a bit long (as do I) so I run several "Early Expire" procedures during the wee hours of the morning to set the expire flag in the SpamFilter DB.  SpamFilter then kills them off on it's next expire cycle.  I am still perfecting this one as it soes seem to load the hell out of SQL server while it is doing the searching.

Regards,

Dan S.