Yeah, that 'undefined' error is really just the player incorrectly reporting some error which is thrown up on the stack. If you do not register a fault handler, it is thrown as an error so that makes sense.
You have autoCommit set to true so the client is committing after each property change event which causes a large number of updates. You probably want to just set autoCommit to false and manually call "commit" after each change. If calling commit is not desired, maybe you just set up a timer to call commit periodically if there are any pending changes. Jeff From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of vdeprojects Sent: Sunday, February 08, 2009 11:06 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: LCDS : Managed associations - creating/deleting new Items It seems that adding a DataConflictEvent.CONFLICT event handler and a DataServiceFaultEvent.FAULT event handler to the data service can prevent the uncaught 'undefined' exception. In my case I simply have to type quickly to run into a data conflict (each keystroke seems to be sent to the server...). Anyone any idea?
<<inline: image001.jpg>>
<<inline: image002.jpg>>
