Albert,
Just before receiving your email, I wrote this below. I appreciate all the suggestions. I decided to do a TRACE on the LOAD instead of the RUN. I found the errors. Five statements when RBASE is setting up comments on a table INVINSERT all leave the first letter of the columns out. Of course that means the table cannot be created since I have no columns with those names. Strangely though, I have no table with that name. I create a TEMP table starting with a tINVINSERT. Plus I do not have comments when I create temp tables. I guess I will have to run this again this with TRACE weekend on the REAL database and fix it. One last question. Can I edit the LOB or ALL file prior to the LOAD and care for the problem? James Belisle ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Jim Belisle Sent: Friday, February 04, 2011 9:04 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Illegal table name I also had another backup from a month ago in another location and compared the views from that to the After load database. Once again I found the same number of views. There are no views missing in the After load database. When I first sent this to the list, I mentioned I had an ACCESS Violation error while creating a new table from an Excel worksheet. It locked up the database and I had to use the TASK MANAGER to get out of RBASE. Since that time, I have created three new tables but none of them are attached to a view. Is there any way this error could be causing this problem? Could my database SEE something that is really not there? James Belisle ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Bill Downall Sent: Friday, February 04, 2011 7:25 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Illegal table name On Fri, Feb 4, 2011 at 8:11 AM, Jim Belisle <[email protected]> wrote: Which tool would I use to find out the offending views? Jim, I'm assuming you have a "before" and an "after" copy of the database. * Connect to "before". * At R> Prompt, type these commands: * OUTPUT ViewsBefore.TXT * LIST VIEWS * OUTPUT SCREEN * (This gives you an alphabetical list of views from before the unload.) * Connect to "after". * At R> Prompt, type these commands: * OUTPUT ViewsAfter.TXT * LIST VIEWS * OUTPUT SCREEN In notepad or RBEdit or printed on paper, compare the lists of views. When you find a view that did not survive the RELOAD, connect to "before" again, and type: LIST VIEW missingviewname Study the SELECT command, after the FROM keyword, to find the views that are referenced. That views that are referenced are now in the after database (unless they, also referred to views, not just tables.), because your original load ran all the way to completion. While still connected to "Before", build a little file that recreates this view: OUTPUT viewname.VIE UNLOAD STRUCTURE FOR viewname OUTPUT SCREEN Use RBEdit to remove the CREATE SCHEMA command from viewname.vie (which will refer to the "before" database name) Connect to the "after" database, and run the viewname.VIE file. Repeat this process for each missing view in the after database, but save the VIE files. You can just run them again after the next reload. Bill
