Bernie: The response I received from RBTI tech support was that the corruption (data and indexes) that my client was experiencing was related to network problems.
It appears that they were right. Our problems seemed to be related to a bad printer driver on the Terminal Server. The bad printer driver would cause short and intermittent database disconnects. Since we deleted and reinstalled the printer driver (beginning of this July), we haven't experienced any data or index corruption. I'm not suggesting that your problem is due to a bad printer driver, but rather that it can be something totally unrelated to R:Base. I discovered that the RBase 6.5++ database is open for corruption not only during write operations, but also whenever an "Edit" or "Enter using" form merely accesses and displays data. I think this is due to the concurrency control that's part of these forms. This susceptibility to corruption due to network interruptions is something that seems that file server based databases are subject to. I think that client/server databases might be more forgiving since the connection can be established by and on the server. I also would think that the use of disconnected record sets would limit the exposure to such corruption. I hope that the RBTI dream team improves the "industrial strength" of R:Base to address these types of data and index corruption. My $.02 Tony Anthony Schmidt, JD President The Computery Ltd. One East Main Street Bay Shore, NY 11706 631-665-8100 Voice 6310969-5988 Fax http://www.computeryltd.com [EMAIL PROTECTED] 08/21/2002 10:06 AM Please respond to rbase-l To: [EMAIL PROTECTED] cc: (bcc: Anthony Schmidt/BayShore/SGU_LN) Subject: Re: Corrupt Indexes David, Why do you feel that it is necessary to pack keys every day. Is this a signal that you suspect the "Industrial Strength" engine has a problem? I have one customer that has corruption repeatedly and I can't get to the bottom of it. I tried Pack Keys once and it didn't help. They are running dos and win 6.5++ 1.851 We've tried rotating the unuse (if there is such a word) of workstations to see if one of them is causing the problem. No positive results so far. Bernie Lis Megabytes, Inc. ----- Original Message ----- From: "David M. Blocker" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, August 21, 2002 9:07 AM Subject: Re: Corrupt Indexes > Because of the importance of indexes, the DAILY backup routine that I have > all my clients do does the following: > > SET MULTI OFF > CONNECT dbname > - abort if you can't connect > AUTOCHK dbname > - abort if problem > PACK KEYS (rebuilds all indexes) > COPY .... (backup) > > David Blocker ================================================ 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/
