I didn't want to use that as I think it is not very elegant. I already solved the
problem by comparing the field contents with the DB data, and
running the handler code only when there are real changes. I was just wondering if
there's a better way.
Thanks.
Danny Epstein wrote:
> At 4:28 PM +0000 11/19/99, Sergio Carvalho wrote:
> >I need to change a field inside the fldChangeEvent handler. The problem is that
>this generates another fldChangeEvent, creating a perpetual loop.
>
> One solution is to set a global flag to indicate that the next fldChangeEvent should
>be ignored.
> -
> Danny Epstein, Applied Thought Corporation
> Have friends with Palm organizers? Get BeamBooks!
> http://www.appliedthought.com/beambooks
--
Sergio Carvalho
---------------
[EMAIL PROTECTED]
[EMAIL PROTECTED]
If at first you don't succeed, skydiving is not for you
