Thanks Ben marc
--- Ben Petersen <[EMAIL PROTECTED]> wrote: > Create a new DB with two tables that have the same > structure as your > problem table. Unload data for your problem table > twice -- once with write > check on, once with it off. Load those two files > into each of your two new > tables. > > In the new DB > > Sel * from WriteChkOffTable whe UniqueIdColumn not > in (sel > UniqueIdColumn from WriteChkOnTable) > > It is possible that Rbase errored out upon its first > problem in the table and > didn't unload rows that it might have otherwise. So > while the above will show > you which rows weren't loaded you should _really_ > have a look at the first > row the unload command would have encountered. > > Ben Petersen > > > > On 12 Aug 2003, at 6:13, marc schluter wrote: > > > Hi all > > > > I think I found the problem. It was a bad row in a > tab > > that had a varchar col. > > > > Is there an easy way to find these bad rows? I > can > > see where this could cause major problems with > users. > > > > thanks for all the help > > marc > > > > > > __________________________________ > > Do you Yahoo!? > > Yahoo! SiteBuilder - Free, easy-to-use web site > design software > > http://sitebuilder.yahoo.com > > > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com
