Guess who's getting near to full delivery :-| Rightly, or perhaps wrongly, I've implemented a system of triggers that records every database change in a backup database (I would'a caught Ollie North as well!).
The way I've done it is using the insert/update/delete triggers. Whilst this hasn't been a problem directly it seems to preclude all the RI built in to VFP, and now it turns out that Codebook (there's hardly anyone over there so I thought I'd raise it here) relies on this for deletes! So, the question, is there a sensible way of "daisy-chaining" (damn, spot the ex-hardware engineer) trigger routines? I s'pose I can imagine a way of coding it, but it feels like it would be messy. Regards Mark Stanton One small step for mankind... _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
