main logo
Subject: Re: comparestate wrong on the first screen
Author: Philippe Sevin
Posted: 2001/04/18 12:06:06
 
View Entire Thread
New Search


<i><font color="#663300"><i><font color="#663300">The memento.setstate in the init of the bizobj picks the wrong data. When I move to the next record, it asks me to save or cancel. After that, the ischanged() method works fine and I can click next/previous without being asked to save.
I would need to force the memento state at the end of the init of the form (this.obizobj.setstate(this.obizobj.calias)) but it's protected and I don't want to start modifying the base classes again.</font></i>

Can you explain why the Init() of the form is causing this problem? Perhaps there are better ways to accomplish what needs to be done.
</font></i>

The bizoj init captures a memento of the first record (the form is based on some buffered table). Then the form is displayed. When I move to the next record, I see that comparestate is trying to match the current record with the first physical record in the table. That is the problem.

 
©2001 Philippe Sevin
<-- Prior Message New Search Next Message -->