larger picture of what the code is doing. It is
more of an architectural question...
--- On Thu, 10/9/08, Jacques Oelofse <[EMAIL PROTECTED]> wrote:
From: Jacques Oelofse <[EMAIL PROTECTED]>
Subject: Re: [development-axapta] Re:CustTable Super()
To: development-axapta@yahoogroups.co
chuckle - true true - that was meant to be a rough example of how to get an
error the original poster was experiencing. :)
--- On Thu, 10/9/08, Murat Bal <[EMAIL PROTECTED]> wrote:
From: Murat Bal <[EMAIL PROTECTED]>
Subject: RE: [development-axapta] Re:CustTable Super()
To: develo
Tony Zeigler
Sent: Thursday, October 09, 2008 5:03 PM
To: development-axapta@yahoogroups.com
Subject: Re: [development-axapta] Re:CustTable Super()
He said it occurs in the super() - which would make sense if he had confused
the system about a prior change.
For instance, if his code elsewhere
Tx for the help everyone!
We found the problem eventually it was something completely unrelated
although was still wondering if there was a way to debug and be able to
track exactly where the error is coming from when it happens in the
super() method.
Cheers,
Jacques
Tony Zeigler wrote:
>
> H
He said it occurs in the super() - which would make sense if he had confused
the system about a prior change.
For instance, if his code elsewhere creates two copies of the CustTable row,
and modifies both before saving, then his second copy will blow up with that
error when he calls super.
F
5 matches
Mail list logo
