Always do your maintenance with a fresh start of windows. Dennis McGrath [email protected] [email protected]
On Mon, Apr 9, 2012 at 6:52 PM, Dave McCann <[email protected]>wrote: > Wow, I opened up a can of it with this post. Great information everyone. > I've been in the habit of working on my project from a network drive and > not always turning multi off so I'm going to change those habits and start > doing structure unloads before schema changes in addition to my regular > backups. I haven't really ever found issues myself with VIEWS after > changes, at least not in recent versions. > > In this particular case, it was odd though, I was able to Unload my > structure and reload it to get a clean database without errors but > immediately had a problem with the PK/FK reference and system table rows > count when I went to change any column in any other table. I finally put > this aside and came back to this yesterday and did the very same thing and > wouldn't you know, no errors when I added a table column! I think > sometimes certain errors put R:base in a funky mood, I've found it better > to exit completely and restart it when things start acting strangely (which > I didn't do Friday). > > > On 4/9/2012 5:55 AM, Bill Eyring wrote: > >> Dave, Kenny >> >> Usually I've seen these problems in views where schema changes to tables >> have been made without first dropping views based on the table changed. >> >> Another instance is in forms where an On Before Design eep that defines a >> view or temp table contains an error. >> >> One way you can check this is; >> >> Backup database to a different directory >> Out DBName.all >> Unload ALL >> Out screen >> >> Edit DBName.all and search for the offending table/view references that >> produced the errors. If nothing is found then try this; >> >> Trace DBNAme.all - when an error is produced note the line # then edit and >> fix. >> >> Also at the R> prompt do a List Pkeys then a List Fkeys, check the >> references and go to the table designer and delete the offending foreign >> key. >> >> Try a List Rules and see if you can find the offending rule and delete >> using >> the Table Designer. >> >> Hope some of this helps. >> >> Bill Eyring >> >> >> >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] On Behalf Of Dave >> McCann >> Sent: Friday, April 06, 2012 11:18 PM >> To: RBASE-L Mailing List >> Subject: [RBASE-L] - strange database errors >> >> I've been up against a wall with a recent database problem on one of my >> projects, hoping I can get some ideas. >> >> Recently my database began having this issue, whenever I go to add a >> column >> or make pretty much any structural change, I get an ERROR - A foreign key >> references a table not known to be referenced (1242), followed by an >> ERROR - >> The number of rows counted was not expected. >> >> I have been able to UNLOAD my structure and recreate the database with >> seemingly no errors, database checks out OK with AUTOCHK and R:Scope >> afterwards, but as soon as I go to edit the structure the errors return. >> >> Running R:Scope the errors are invalid row count errors in SYS_RULES, >> SYS_CONSTRAINTS, and SYS_COMMENTS. I suspected something wrong with a >> constraint or rule because I've made adjustments in those areas in the >> last >> month and since the initial error indicates a problem with a foreign key. >> >> Any ideas about how I could go about narrowing down the specific >> problem? Since everything was valid when setup, and again when >> structure was recreated just not quite sure why/how this could be >> happening. >> >> >> -- >> Dave McCann >> >> >> > -- > Dave McCann > Classic Micro Systems > > >
