johnf wrote: > On Friday 19 September 2008 12:01:46 am Uwe Grauer wrote: >> I use triggers (in this case "after insert") for this kind of thing. >> Together with a transactional database this method should work for you >> too depending on you "something" you have to do. >> >> Uwe > > Yes many times a trigger can help. In this case it would not. The something > > has nothing to do with data. It was needed to send an email. It's true > that emails can be sent from the database. But the client does not want that > to happen. But that's not the only time I had the need. I was just > wondering about the general approach. >
For me the general approach is storing it into the database as this is the central place for a system. I often used worker clients which were used do do the actual work which has been placed into special tables. This way you can make sure that nothing gets lost and everything can get logged for review. Of cause this is a approach for multiuser systems where you need to have central processing instead of doing everything in one client. Uwe _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
