Error when deleting the last record out of a file

[Jeff Harrison]

--- "Jay R. Ashworth" <jra at baylink.com> wrote:

> On Thu, Dec 20, 2007 at 09:33:48AM -0800, Jeff
> Harrison wrote:
> > > "Must fill" isn't an attribute of columns; it's
> an atttribute of
> > > screen fields. Since there can be more than one
> screen that contains
> > > a field, and "must fill" is independently set on
> each, you cannot,
> > > in fact, safely make that assumption in the
> abstract, no.
> >
> > You could, however just choose a field that "must"
> have information in
> > it in a valid record. @cd comes to mind for
> example.
> 
> This is true.
> 
> Now, just to win the argument (:-), I'll point out
> that even that won't
> work if you're creating a new record, and want to
> make sure you didn't
> run out of disk space.
> 
> And isn't there some place you can look to see *why*
> a lookup to a
> record that's supposed to exist failed, which you'll
> be deprived of it
> you use this shortcut?
> 
> Cheers,
> -- jra
> -- 

Yes, I think it is best to always use the -n flag and
handle the error yourself.  That is my personal
preference anyway - Except I must admit that I usually
don't bother on the free lookups - I just use the -e
flag and let filepro handle it.

As to why the lookup failed - how many reasons can
there be?  I can think of 3:
#1 Record is not in the index lookup.
#2 Disk is full on a free lookup.
#3 you used the -w flag and the record is locked

Filepro provides the locked() function for the last
instance.

Jeff Harrison
jeffaharrison at yahoo.com

Author of JHImport and JHExport. The fastest and
easiest ways to import and export with filepro. 


      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs