Hi Razzak The concomp db worked fine. But I got a good unload file and rebuilt the db, did a full autochk, no errors.
Then unload all works fine. run this file SET ZERO ON SET WRITECHK ON SET CLEAR ON Now do another unload all and the out put file is smaller. If rebuild the db from this smaller file soome of the rows are missing. Why would the above settings change the unload output?? What should I look for next? marc --- "A. Razzak Memon" <[EMAIL PROTECTED]> wrote: > > At 07:10 AM 8/8/2003 -0700, Marc Schluter wrote: > > >well folks > > > >I think I found my problem. > > > >If I start RBW then do Unload all, everything is > OK. > >Then I run > > SET ZERO ON > > SET WRITECHK ON > > SET CLEAR ON > >and the output file is smaller and I loose the > rows. > >Then I set writechk off and did another unload all > and > >it worked fine. > > > >It seems that writechk on will not allow all of the > >rows to be written to the output file and it > appears > >to be the tables with dates. > > > >Am I crazy or is this possible? > > > Marc, > > SET WRITECHK ON specifies R:BASE to verify "EVERY" > write to disk. > > So, you may need to check integrity of your database > using R:SCOPE. > > Just for fun: > > Try the same scenario using the CONCOMP database > bundled with the latest R:BASE 6.5++ for Windows, > i.e., C:\RBTI\RBWIN65\SAMPLES\CONCOMP and see what > happens. > > Have Fun! > > Very Best R:egards, > > Razzak. > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com
