dclerk aborts on scan/selection - why?

[Jeff Harrison]

--- "Larry S. Weaver Jr." <lweaverjr at dellem.com>
wrote:

> Jeff Harrison wrote:
> 
> >--- "Larry S. Weaver Jr." <lweaverjr at dellem.com>
> >wrote:
> >
> >  
> >
> >Hi Larry.  Have you tried this with another
> selection
> >set?
> >
> I tried it with just the @cb and @cd, and then again
> checking only @ub
> and @ud.

And what was the result?  Still failing with "Abort" ?
 If so I would say it is not a corrupted selection set
causing your problem.

> 
> >  Another Qualifier?  
> >
> I didn't try it on another qualifier, but I did try
> it on another file
> (invc21) and had the same result.

Ok, then it is probably not corrupted data, however I
can't say that you have ruled that out entirely.

> 
> >I would also try running
> >this without processing and see if you still have a
> >problem.  
> >
> No processing involved.  I'm just trying to get the
> records to display
> in a browse.  I can get the same result by going
> into the file through
> the IUA menu, selecting an index, pressing "B" to
> display the records in
> a browse and then pressing "S" to run the selection
> set on the browse.
> Doing this results in the same abort (but takes a
> lot more key presses
> than running it from the command prompt ;-).

I still suggest that you try running this without
processing.  Just add -y none -z none to the command
line.  Remember that automatic processing runs
whenever you access the record in non-browse mode.  It
sounds like it is running at least one time here. 
Also, remember that the auto and input processing
table are loaded into memory when you first go into
dclerk, so even though it may not be executing at the
time of your error, you can't say that it is not a
factor until you do this.

> 
> >Also, if it still aborts try re-naming any
> >automatic indexes that you have to (for example)
> >hldidx.A, hldidx.B, etc.
> >
> Not sure what you mean by this.

Your automatic indexes are accessed AUTOMATICALLY, of
course, when you go into dclerk.  I was trying to
eliminate corruption there as being part of the
problem, so if you delete all of your automatic
indexes or rename them as I described above then you
will eliminate this as a possibility.

In my experience type of thing is usually related to
one of four things.  
#1 bad index(es)
#2 bad key or data (or data does not match map)
#3 a problem in the processing.
#4 an other corrupted file that is being accessed.

So I would go about trying to eliminate these
possibilities where you can.

> 
> >  By the process of
> >elimination we may get an idea of what is causing
> your
> >problem.
> >
> >Good Luck.
> >
> Thanks!
> 

Your welcome.

Jeff Harrison
jeffaharrison at yahoo.com

Author of JHExport and JHImport.  The easiest and
fastest ways to generate code for filePro exports and imports.


		
____________________________________________________ 
Yahoo! Sports 
Rekindle the Rivalries. Sign up for Fantasy Football 
http://football.fantasysports.yahoo.com