RE: Debug %found and other BIFs

That's true, Barbara, but there may well be times especially in debugging
that I want to set those flags just to quickly test severe error conditions.
This happens often in boundary testing where I really don't want to have to
purposely corrupt the database, but I want to make sure my code executes
properly in case it does get corrupted.

With indicators, it's quite easy to feign a missing master record.  With
BIFs it's much more difficult.

Joe

> From: Barbara Morris
> 
> Buck wrote:
> >
> > A related question is this: How can I change the value of %found?
> >
> > If %Found();
> >     ... do some code
> > Else
> >    ... do something else
> > EndIf
> >
> > Let's say I am debugging and I want to force one branch or the other...
> 
> But there's more to %Found or %Eof than just the setting of the bif.
> Depending on what caused the bif to be set, records might have been
> locked or released, files might have been repositioned (or not been
> repositioned), program fields might have been changed.  If you force
> your code through a different branch, but the state of the file and
> program fields are according to the true branch, you could create
> problems that would not ordinarily exist.