On 9/Mar/2010, at 2:18 PM, Mike Schrag wrote:
> these don't look like actual exceptions, they just look like the stack traces
> from where the debug statement occurred ... these things should always say
> that in their exception message IMO
>
> On Mar 9, 2010, at 5:03 PM, Johan Henselmans wrote:
Yep. Patches welcome :)
Cheers, Anjo
Am 09.03.2010 um 23:18 schrieb Mike Schrag:
> these don't look like actual exceptions, they just look like the stack traces
> from where the debug statement occurred ... these things should always say
> that in their exception message IMO
__
these don't look like actual exceptions, they just look like the stack traces
from where the debug statement occurred ... these things should always say that
in their exception message IMO
On Mar 9, 2010, at 5:03 PM, Johan Henselmans wrote:
> While trying to find out why some data did not get s
While trying to find out why some data did not get saved. I discovered in Debug
mode that all kinds of fetches did return an exception, which in turn caused
the ERXEC to not do it's thing and save the data in it's EOEditingContext.
Removing the fetches that created the Exceptions in a RR-loop r
