dclerk aborts on scan/selection - why?

Christopher Yerry christopheryerry at yahoo.com
Mon Jun 27 12:23:51 PDT 2005


|OS:    SuSE 9.2, KDE 3
|fp:   5.0.09D4
|
| From the command prompt:
|
|dclerk deliv2 -m ma -xie -xs t -s1 -b -t 400000
|
|the "ma" qualifier on deliv2 has 40,987 records.
|
|t.sel:  Scanning for records created or edited by user Dericka on 05/18/05:
|
|(a and b) or (c and d)
|a:@cb:eq:dericka
|b:@cd:eq:05/18/05
|c:@ub:eq:dericka
|d:@ud:eq:05/18/05
(Shortened)
 
Larry 
 
If you have not solved this 2 things I would recommend, because what you are doing should not be this hard 40,000 records is not allot. I personally do not believe this is a token or a selection problem. It sound to me more like a corruption problem
 
1 Write the selection as a process and see if there is still a problem  
 
2 Rebuild the data file This can be done in filepro and (contrary to popular belief) all the original information can be retained ( @cd, @UB  etc). I would be glad to send you the procedure if you do not know it its simple!! You an also clean out the "deleted" records that are never cleaned and rarely re used properly
 

also You cannot do anything with an index if someone is in the file (aka the lockfile). They do get confused allot I clean mine out every night.
 
Christopher Yerry
CM Consulting
 
 



		
---------------------------------
Yahoo! Sports
 Rekindle the Rivalries. Sign up for Fantasy Football
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.celestial.com/pipermail/filepro-list/attachments/20050627/8e5d0fcd/attachment.html


More information about the Filepro-list mailing list