By: Erik Paulsson

Erik Paulsson — Tue, 19 Feb 2008 08:39:28 +0000

You are of course correct, I guess my example using a method that only refreshes the caller object might not have been the best one. But I think it’s useful to know how to run methods on the caller object, whatever they might do, create, delete or refresh. It’s also useful to know how to differentiate between callers, in case the class, form or report may have different ones.

I like to looks of you blog by the way. I’m going to take a closer look when I get the time. Looks very ambitious and well structured.

I really don’t know why the first part of my text is in bold text, it’s not supposed to be, looks a bit like I’m yelling at you.

Thanks for your feedback, always appreciated!

By: Björn

Björn — Mon, 18 Feb 2008 19:03:42 +0000

Personally I prefer doing everything in the class like this:

if (args.record().isFormDataSource())
{
args.record().dataSource().refresh();
}

That way all the code is in 1 object and you avoid reflection to check if a method exists.

Comments on: Refresh caller form

By: Erik Paulsson

By: Björn