On Sunday 17 February 2008 10:03:49 am Ed Leafe wrote: > On Feb 17, 2008, at 11:49 AM, johnf wrote: > > I really could not figure out what caused the problem. It is > > diffcult to > > follow events in Dabo. But I was able to determine it had something > > to do > > with my VCR Class (VCR buttons). > > That's simple enough to start debugging. If the VCR button is the one > for 'next', then override the form's next() method to say: > > def next(self, dataSource=None): > print "form next() called" > super(MyFormClass, self).next(dataSouce) > print "form next() done" > > Do the same for the form's activeControlValid(), update() and > refresh() methods. The next time that you run the form and get the > error, you can get a good idea as to how far along the process got > before the error happened. Do that a few times; if the error always > occurs at the same point, then you've cornered your suspect. If not, > then you have to start digging into stuff like refresh() and update() > for your controls. > > > The funny thing is I have been using the > > Class on other forms without issue. But on this form it caused the > > Form.Close() method not to work correctly. > > Sounds like the problem isn't in the VCR class, but in the code that > it triggers in your form. > > -- Ed Leafe
> Sounds like the problem isn't in the VCR class, but in the code that > it triggers in your form. Right! But the VCR's work perfectly. And I don't have to use the VCR button only create an instance to cause the error. My VCR's are not using the Forms next(), last(), etc.. I did not use the forms next() because next() was not returning the records in the order I wanted. For example on my customer screen I wanted the next() button to return the next record in alphabet order, and the purchase order screen to return the next PO in a numeric way. Creating the instance causes a bizobj requery on my meta-data for the form. Then when the user clicks on the next button the Class sets "setWhereClause" to the correct record. And then a simple Form.requery() happens. This form has four different lookups, with 60-70 fields from 7 different tables (not including the standard meta-data tables). If the user can't find the right record with four lookups then I doubt a VCR class is going to help. Don't get me wrong I'll continue to look for this bug because I'm sure it must be effecting the other forms. But for now I'm happy I got it Close() -ing correctly. -- John Fabiani _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
