Flex 2.01 .net weborb: Wacky error messages on client browser

[Wayne_1977]

Hi folks,



I'm new to flex, and I'm trying to get a flex client to talk
to my .net back end via weborb. I've got a few simple test cases
working ok, but with more complex code I get a pop-up on my
(firefox) browser:



TypeError: Error #1010: A term is undefined and has no
properties.

at orbTester/gotServerData()

at orbTester/___Operation3_result()

at
flash.events::EventDispatcher/flash.events:EventDispatcher::dispatchEventFunction()

at flash.events::EventDispatcher/dispatchEvent()

at mx.rpc::AbstractOperation/
http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent()

at mx.rpc::AbstractInvoker/
http://www.adobe.com/2006/flex/mx/internal::resultHandler()

at mx.rpc::Responder/result()

at mx.rpc::AsyncRequest/acknowledge()

at
::NetConnectionMessageResponder/NetConnectionChannel.as$40:NetConnectionMessageResponder::resultHandler()

at mx.messaging::MessageResponder/result()



So a few questions:



1) What does this error message mean?

2) How can I find out what line of my flex code is generating
it

3) Is there a way to get decent error messages from this
environment?



Many thanks,



ws

[Former Community Member]

A line in your gotServerData() function tried to access a
property from that

was undefined. You should look through the lines of code in
this function

and start testing to see what may be == undefined before
accessing any properties.



private var someObject:*;



private function gotServerData()

{

var foo:Object = someObject.someValue; // If someObject is
undefined,

accessing someValue will cause the error your seeing

}

[Wayne_1977 · Accepted solution]

Thanks Peter - I've found and corrected the problem.