Could you please be a little more specific? My application uses 3.3, though I could update to 3.4, however the swfs I am loading are legacy content and I have no way of changing the Security.allowDomain("*"); that they contain.
Are you saying that the only way to solve the problem would be to use 3.4 for my application and to change the code in all the swfs I am loading?
Just to clarify, the SWFs I am loading are not Flex SWFs, but AS3 only swfs with a small document class.
AllowDomain really works on a per-SWF basis. If the SWFs you are loading are monolithic (one swf, no RSLs), then once they grant access via allowDomain, all other SWFs loaded from that domain are allowed access.
I assume you switched the main app to using RSLs. In 3.3, there is no way to have code in the RSLs call allowDomain. In 3.4, calling systemManager.allowDomain calls code in the RSLs to tell them to call allowDomain as well.
Flex SDK Developer
Adobe Systems Inc.
Thanks for clarifying. Running the main application on 3.4 and calling systemManager.allowDomain("*") has solved the problem. I can now access the loaded swfs freely and without any Sandbox errors being thrown.
One thing I am a little unclear about though is why the application should need to grant access to the loaded swfs. The scripting is asymetrical - the application accesses properties on the loaded swf, but they don't access any properties on it?