Problem with Shared Object data access

We had a problem in a recent game project getting SharedObject to store the players progress. When we tested it in Flash Builder it worked fine but as soon as we uploaded the game to our server (or any server) the data were not saved. We found out that to avoid name conflicts, Flash looks at the location of the SWF file creating the shared object. The solution to our problem was simple. By setting the local path to “/” We opened communication between the files. This means of course that all files in the same domain can access the object, so you have to watch out for conflicts if you have other projects on the same domain.

To avoid inadvertently restricting access to a shared object, use the localpath parameter. The most permissive approach is to set localPath to / (slash), which makes the shared object available to all SWF files in the domain, but increases the likelihood of name conflicts with other shared objects in the domain. A more restrictive approach is to append localPath with folder names that are in the full path to the SWF file. For example, for a portfolio shared object created by the SWF file at www.myCompany.com/apps/stockwatcher.swf, you could set the localPath parameter to /, /apps, or /apps/stockwatcher.swf. You must determine which approach provides optimal flexibility for your application.

Read more here