This content has been marked as final. Show 4 replies
dunno where your inputs are defined, but i notices that "this." went away around the point where you commented out. it would matter if those pieces are defined outside of this' scope.
The use of 'this' or not has no real relevance. Adding 'this' was part of the troubleshooting process with 0 affect. Inputs are defined as part of the mxml form all part of this application. The data object is fine all the way upto the 10th element even if I step through the debugger line by line. Hit the 11th element, throw an error.
well, you're getting a null exception. and since it's obvious that outDataSet is not null, it must be the other object you're referring to. i'd double check the spelling of your component's id and make sure it is in fact "AgencyAddrOne" - maybe you missed the 'r'?
if AgencyAddrOne is in an included component (a separate mxml/as file), it might be out of scope, such that you would have to do MyAddressComponentId.AgencyAddrOne
also, unrelated, if you're building a sql update statement on the server side, be careful of sql injection.
Thanks for your input, but I figured out the issue. My input for the data is a tab navigation form and the object was failing for data points on a different tabs. My error was assuming the data would be active on all tabs regardless of the selected one. I was wrong.