In your code, vchk_result will always be 0 when you check it, because the CLS completed correctly. My solution to this is to do this sort of thing:
SET ERROR VAR vErrVar SET VAR vErrSave INTEGER OUTPUT Autochk.log with screen AUTOCHK dbName FULL SET VAR vErrSave = .vErrVar OUTPUT SCREEN -- this also set vErrVar to 0 CLS --etcetera Ramsour Mike <[EMAIL PROTECTED]> wrote: >Part of a routine that I do each day is to reload my database, run AUTOCHK >on it and if everything comes out OK I then copy the database to a network >share for my users. �During this morning's run I encountered a problem where >the RB2 did not get entirely reloaded and none of the indices were rebuilt >but AUTOCHK apparently gave an OK result so that the copy took place. > >Here is the code that I use: > >DISCONNECT >-- >CLEAR ALL VAR now >-- >SET ERROR VAR vchk_result >-- >OUTPUT d:\autoload.$$$ >-- >AUTOCHK maindata FULL >-- >OUTPUT SCREEN >-- >CLS >-- >IF vchk_result <> 0 THEN > �-- > �CLS > �-- > �OUTPUT d:\loadrslt.txt > �-- > �WRITE 'Errors encountered during data loading -- aborting' > �-- > �OUTPUT SCREEN > �-- > �GOTO endline > �-- >ENDIF >-- >CONNECT maindata >-- >RUN mon_calc.prg >-- >RELOAD NEXTDATA >-- >DISCONNECT >-- >OUTPUT d:\autoreld.$$$ >-- >AUTOCHK nextdata FULL >-- >OUTPUT SCREEN >-- >IF vchk_result = 0 THEN > �-- > �CLS > �-- > �OUTPUT d:\reldrslt.txt > �-- > �WRITE 'Database reload successful' > �-- > �OUTPUT SCREEN > �-- > �DELETE MAINDATA.* > �-- > �RENAME NEXTDATA.* MAINDATA.* > �-- > �COPY MAINDATA.* m:\rbased~1 > �-- > GOTO endline > �-- >ELSE > �-- > �CLS > �-- > �OUTPUT d:\reldrslt.txt > �-- > �WRITE 'Errors encountered on database reload' > �-- > �OUTPUT SCREEN > �-- > �GOTO endline > �-- >ENDIF >-- >LABEL endline >-- >EXIT > >The database files are somewhat large by some measures: > >MAINDATA.RB1 �169,196 >MAINDATA.RB2 �805,486,492 >MAINDATA.RB3 �201,887,774 >MAINDATA.RB4 �1,126,400 > >My concern is that the files are getting too large or that I have something >wrong with my system or possibly the database. �If there was an error in the >database then why didn't AUTOCHK catch it? �I am running the latest version >of R:Base for Windows on a Windows 2000 PC. �Could there be a problem with >an index file being that big? > >As an aside, will v. 7.0 also be limited to around 2 GB or will that limit >be lifted? > >Thanks > >Mike Ramsour >AK Steel Coshocton Works > >740-829-4340 >================================================ >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/ > __________________________________________________________________ Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/ Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.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/
