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. For instance something along this line should do the job: CustTable custtablea; CustTable custtableb; ; select custtablea where recid = 1; select custtableb where recid = 1; custtablea.name = "Changed"; custtableb.name = "ChangedAgain"; custtablea.save(); custtableb.save(); In this example I believe custtableb will blow up with his error when it calls the super()... Since the actual root cause of the error is outside the super() it can be a pain in the arse to track these down....
--- On Wed, 10/8/08, Brandon Boman <[EMAIL PROTECTED]> wrote: From: Brandon Boman <[EMAIL PROTECTED]> Subject: [development-axapta] Re:CustTable Super() To: [email protected] Date: Wednesday, October 8, 2008, 10:44 PM Hi there In which method does the error occur? Brandon Boman System Analyst / Developer iSoft Technologies (Pty) Ltd by WellPoint Systems Inc. 49 Sovereign Drive, Route 21 Corporate Park Irene x30, South Africa Phone +27 (12) 345-4750 Fax +27 (12) 345-4252 Email: brandon.boman@ wellpointsystems .com www.wellpointsystem s.com <blocked::http://www.wellpoin tsystems. com/> [Non-text portions of this message have been removed] [Non-text portions of this message have been removed]
