Re: bad systable on SE 5.0

On Tue, 23 Jun 1998 15:48:09 GMT, davek@summitdata.com (David Kosenko) wrote: >Since Axel indicated that all the entries in syscolumns already had a tabid of 312, >that *should* do the trick. Of course you need to be sure that there are no other >entries in the system tables referencing tabid 246, else there could be other >problems. But as long as systables is the only catalog affected, the above shoudl >work fine. Thanks for you advice but I had no luck. I can *select* the bad systable and view its contents but that's all. No *update*, no *delete*, nothing (but an error). BTW, I think, an update of the tabid in systables is not possible, cause this is a "serial" field ? I updated the syscolumns and all other tables to the *old* values and renamed the .dat file. I can access this table now, but the systable is *still* defect, so I think I have to rebuild the complete database :-( >The big question is WHY did systables get into such a state? Yep. THX Axel -- Dies ist der automatische Signaturbeantworter. Die hiesige Signatur befindet sich in Urlaub. Bitte hinterlassen sie Ihr Benutzer- kennzeichen und Passwort nach dem Zeilenende. Vielen Dank.