On Feb 16, 2010, at 4:41 PM, Sim Zacks wrote:
> The reason it was in the afterInitAll function is because I saw that
> posted on some old messages on the mailing list. Is there any reason why
> the requery should be in the afterInitAll instead of the afterInit?
Not really; it depends on the particular needs of your app. In your
case, your requery was coming after your call to new(), which was not what you
needed. There is really no benefit to afterInitAll() unless you need to
reference any controls on the form in that code, which won't exist when
afterInit() fires.
-- Ed Leafe
_______________________________________________
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/[email protected]
