Actionscript 2 :: Opening Other SWFs Using Relative Paths On Networked Drive

We cannot seem to get an original .SWF to load its partner .SWF files.While the <object> tag will load its file properly, the .SWF cannot load other .SWFs into it.The ActionScript is autogenerated via AS2 "Behaviors", and basically calls either loadMovieNum(file, this) or this. LoadMovie(file), depending on how it was loaded previously. Each group of .SWFs that reference one another will exist on a drive-mapped network share.A Client is using the "Behaviors" feature of ActionScript 2.0Said behavior is to load other .SWF files in the same path depending on an onRelease() event Neither the Client, nor ourselves, are fluent with Flash & ActionScript.The .SWF will be hosted in HTML inside of a custom application.The software programmatically loads HTML from a stream, not a file.Said HTML uses the standard <object> tag to host the Flash .SWF.The primary .SWF is located underneath a mapped networked drive (example: "K:") in a series of subfolders.The group of .SWFs will reside in the same folder Our controlled environment is WinXP+SP3 and Flash 9, with extremely-limited ability to update.They are strongly against using absolute paths, as it will affect reuse of certain .SWF groups.

Using Process Monitor and dabling with the "base" <param>, we have seen the following: Without the param, it tries to find the .SWF as a Registry value underneath AboutURLs. This is likely a side effect of our app initially pointing to "about:blank" before dynamically loading the HTML.With the full path ("Kestsub") as base, it tries to find the SWF on the root of the "C:"Testing with a real HTML file (not yet able to test with the App), providing a full path without the drive letter ("estsub") will navigate to this path from the same drive as the HTML. Given our limitation (the "about:blank" thing), this probably will either be the "C:" OR the Registry. Is this possible by using any HTML/ JavaScript on our end, or will we have to have some ActionScript that will determine the current SWF's path, use that to dynamically obtain the location of the other SWFs (also in the same path), then try to teach this Client how to implement the script? Again, they (and we) know little about Flash; they used "Behaviors" to try and get this to work.