"...Security error ..." Typically indicates a security
Do you understand about the Flash Player security sandbox
architecture, and crossdomain.xml policy files?
Some additional observations:
I advise setting resultFormat="e4x" and working with XML. The
default causes Flex to create a tree of dynamic objects. This is
rarely the best solution.
When binding to a result (which I strenuously advise against)
With binding, once you get the security issue behind you, if
your data does not display, you are screwed. There is no way to
debug the problem.
Instead, use a result handler function. First, you will know
your call has returned. Second, you can inspect the format using
toXMLString(). Third, you can craft and test the dataProvider and
dataField specifications. And do other stuff too.
Do make sure you can hit the ?wsdl from a browser.
I am using .net weservices with Flex fairly heavily at the