what's your url and what needs to be done to see the problem?
1 person found this helpful
Almost always when something works locally but not on line... it's a path problem. And I see that you are accessing your .swf from a sub file.... nothing at all wrong with that, but you do need to understand how pathing in Flash works:
Almost always when it works on the local machine and not the server, it's a pathing problem.
You can put your Flash related files in whatever folders you want, they do NOT have to be in the root, they do NOT all have to be in the same folder. But if you have a problem and if sticking them all in the root folder works, then you know that the issue was a pathing problem.
Just remember that paths used in the .swf become relative to the Web page on which the .swf is placed, NOT it’s physical location. So for example, if your .swf is in the flash/data folder and you use that .swf on a Web page in the root folder, you are in effect, removing that .swf from flash/data and putting it in root. So if the .swf is loading any related files (xml, images, video, etc), the path used inside the .swf to load the .xml file has to be relative to it's new location in root and then back down into flash/data. This is true even though when testing the .swf by itself, it can be inside flash/data and work just fine, since relative to it's location, the path is just fine, they are in the same folder. But if that same path is used when the .swf is placed on a page two folder levels up, the relative path has changed, the old "same folder" path will not work.
In fact if you are placing the .swf on a web page in a different folder than the .swf is stored in, and that .swf calls external assets, then direct clicking and opening of the .swf in it’s folder should NOT work! That’s because the paths to the external assets should be relative to the Web page and not the physical location of the .swf.
So just be sure that you use addresses relative to the final Web page locations (not physical file locations) and you can put the Flash related files in what ever folders you want.
Eye for Video
1 person found this helpful
It could also be a case-sensitive issue. I was running a project that references audio files in a folder called "Audio". It worked fine locally, but not on the server. The AS references has a small case "a" in the path, so I had to change the folder name to match and it worked. Pat ing issues can be confusing as well as pointed out above. My usual method just to make things easier, is to put all the flash files in a single folder and the HTML page that hold the main SWF. This means I don't need anything except the filename for any external SWF that I need to load using either loadMovieNum or loadMove. (note, I also find it better to load the external movie into an empty movie clip in my main SWF, it just easier to keep track of variables without introducing the level into the mix)
Thanks guys. Yes, I definitely uploaded the entire project the same as it existed on my drive/Dreamweaver directory. And there was no change in case. The odd thing was that it worked before and then several files wouldn't work. I believe the problem was permissions related because now it works with no changes by me. I think the service provider must have had some problems. Thanks. Now on to the programing issues that are normally difficult.