I have one situation where the index always gets corrupted which is replicable but I have not reported it to RBTI as it must be my fault.
What happens is that I have an EEP which runs on leaving a row on a multi-row form which crashes R:Base without fail IF a specific condition is met. I haven't found a way to overcome it yet but it's only a matter of time... However, when this occurs the index for a table not used by the form (and to which I _should_ have added a row) gets corrupted. The only solution is to RELOAD - PACK KEYS does NOT work! (It fails with a Cannot Connect to Database message although the database is already happily connected.) I think that I can say that I have never had index corruption without a preceding crash. Equally, I have never had R:Base crash as much since changing to the Windows version. The Dos version rarely, if ever, crashed. RBW6.5++p3(beta3) (10/08/2002) is no better nor worse than anything since the original 6.5++. Hope this gives you a clue... Regards, Alastair. ----- Original Message ----- From: "J.M. GRATIAS" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, August 21, 2002 10:56 AM Subject: Corrupt Indexes > > William : > > >> > Just a follow up to the corrupted text indexes - we have been bitten again > by this bug. I have never in my years of experience with R:Base had so > many index problems, until (it seems) that we began to use long text values > for keys (Text(36)) - perhaps R:Base is having trouble with these. > << > > Yesterday a client complained about a report that print twice the same > rows. > They send me a DB backup and the problem comes from a corrupted index on a > TEXT (4) FK > No concurrent activity (SET MULTI is OFF and app is installed on the local > drive). > > Using RBW6.5++ (build 1.851xRT03). > > An other client had the same problem last month .... > > I have the feeling (may by wrong) that the problem is more frequent now > than it was with older versions. > > > Is there a simple way to detect the problem (AUTOCHK is no help for that) ? > It is important for me to detect the problem before printing wrong reports > .... > > To correct it, I ask then to do a RELOAD, which is not a trouble because up > to now I have no multi users on the same DB. > > TIA, > > J.M. GRATIAS, Logimatique > ================================================ > 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/
