CompuServe test bed

CompuServe Thread

Amiga Vendor Forum · Precision Software

SBPro4

10 messages in this thread
#31381From: Loren A. BuschDec 8, 1991 2:49 PM
I have encountered a major problem with corrupted files that I have never had before in SBPro/Amiga (had it occur on the C-64, not with Amiga versions). That is 'error in postioning in file' followed by errors deleting a record (100 and 101). Seemed to have been caused by trying to import a record with a duplicate key for a unique index and the record was kept in the file but not indexed. A REORGANIZE DID NOT CURE THE PROBLEM!!! Had to export the entire 14,000+ record file and re-import to get the files cleaned up. Have encountered this twice now, luckily the second time was a small file that was easily fixed. Has anyone else been having this type of problem, or does anyone know what I need to avoid to stay away from this one?
#31477From: Mike/CompuStore W-GermanDec 10, 1991 4:23 AM
Try this one: Project/Remove/index (whatever index was used by the time the error occured) Project/new/index (the same one again) this did work very well for me.. try it -Mike CompuStore GmbH |Fritz-Reuter-Str. 6 |CI$ 71001,210 |Tel: +49 69 567 399 Michael Metz |D-W6000 Frankfurt 1 |BIX: mimetz |Fax: +49 6 ael Metz |D-W6000 Frankfurt 1 |BIX: mimetz |Fax: +49 69 560 17 84
#31484From: Pat Cummings, OXXIDec 10, 1991 10:21 AM
We're finding this to be an answer for a LOT of problems with SBp4 — just regenerate the index! Regards, Patricia Cummings @ Oxxi (310) 427-1227
#31655From: Loren A. BuschDec 14, 1991 12:45 PM
See previuou reply: didn't help on this one, first time in years (yes, years)
#31654From: Loren A. BuschDec 14, 1991 12:45 PM
Tried deleting/rebuilding the index twice, no help on this one. Like you I have had good luck with that remedy before, but not this time.
#31701From: Mike/CompuStore W-GermanDec 15, 1991 7:09 AM
Loren, then the only way to keep your data is to export/reimport the data. Have you tried to reorganize or create an empty copy of the file and import data into the new file? Good luck -Mike CompuStore GmbH |Fritz-Reuter-Str. 6 |CI$ 71001,210 |Tel: +49 69 567 399 Michael Metz |D-W6000 Frankfurt 1 |BIX: mimetz |Fax: +49 6 ael Metz |D-W6000 Frankfurt 1 |BIX: mimetz |Fax: +49 69 560 17 84
#31710From: Loren A. BuschDec 15, 1991 12:17 PM
This thread is getting long! Expot/Import solved the problem. I put the message up to see if any others were having the same problem and might have been able to pinpoint the cause or conditions that were causing it. In my case the problem seemed to be associated with the file keeping a record with a duplicate key after the error requestor was canceled and attempts to move within the file gave me a 'This record has been modified, do you want to save it?" message. I also wanted to point out that REORGANIZE did NOT work in this case! – via Whap!
#31615From: SPC Superbase Tech SuppDec 13, 1991 10:25 AM
Re: Corrupted files Remove the first index, replace it. Remove the second index, replace it. Etc….Through all of your indices. This should help. Darin, SPC Superbase Technical Support – via Whap!
#31659From: Loren A. BuschDec 14, 1991 12:58 PM
Darin: First, I appreciate your continued assistance here considering the changes in ownership, etc. I tried that, got rid of each index one at a time, rebuilt the primary keys, etc, still no luck. Even REORGANIZE carried the problem with it. Export/Import was the only solution.
#31801From: SPC Superbase Tech SuppDec 17, 1991 10:56 AM
Hmmm. Very interesting. Oh well, it works now, so I guess that's what matters. Re: my continuing support. No problem. I enjoy supporting SBPro4. Darin, SPC Superbase Technical Support – via Whap!