I'm not on a network, so I didn't have data problems. In going on a network, I would be using local log files/tables and posting to the file server with may be a lock and load with full use of the ERROR VARIABLE to follow completion problems. RRR
----- Original Message ----- From: "Harlan Haynie" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, September 23, 2002 3:04 PM Subject: RE: Increasing the fault tolerance of file server databases. > We use several techniques, sometimes we log information to R:Base > tables, such as access logs, recently, we have implemented some stored > procedures that write keystroke info, variable information, ad other > details to log files somewhat modeled after the MS NT event logs. These > log files have proved to be extremely useful. The most complicated > situations to troubleshoot are inserts that fire nested triggers, > especially on the internet side. Writing to a file in Oterro should > help a lot. > > What do you do? > > Harlan > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > On Behalf Of Ron Rose > Sent: Monday, September 23, 2002 1:31 PM > To: rStreet > Cc: RBase List > Subject: Increasing the fault tolerence of file server databases. > > In looking at some of the problems that are being talked about over the > lists, a different way of programing may be needed. I have not seen any > comments of programing the databases with audit trails which may solve > some > of the data corruption problems. Does any one use a more fault tolerent > method? > RRR > > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
