Problem solved. I basically started from scratch, moving bits and pieces of the movie to a new version.....
You were of course correct, Ned, regarding the location of the main .swf in relation to the html page that loads it -- that was my first mistake.
I got the gist of the rest of your explanation when I did a little "substitution" in my mind when looking in each of the external .swfs at the path in relation to the main movie's .swf.
Here's my folder structure:
index.html
mainMovie.swf
/assets
/content/
bio.txt
news.txt
/css/
bioStyle.css
newsStyle.css
siteStyle.css
/fla/
bio.swf
networks.swf
news.swf
I think my troubles sprang from my calling and loading the related .txt and .css files from the movies themselves, bio.swf and news.swf. In each of the movie's frame 1 I would use the path...
var newsURL:URLRequest = new URLRequest("../content/news_10Feb2012.txt");
thinking because the individual movie was doing the calling and loading the path would need to go from the movie, out of the fla directory and into content.
.... If I instead used
var newsURL:URLRequest = new URLRequest("assets/content/news_10Feb2012.txt");
the movie would publish.
From a best-practices perspective should I be calling and loading related .txt and .css files from the individual movies, or from the main movie, keeping the external swfs empty save for the text fields, scroll bars, background images, etc.?
