Document-relative paths to Flash objects in locked regions fail to resolve in child pages after converting template for active content

TechNote: If you have a template that has active content (for example Flash Player content) in a locked region, and you convert the template for active content in Dreamweaver 8.0.2, the document-relative path to the active content is incorrect in the child pages of the template. For example, in the template child page, the document relative path to the SWF file should be myobject.swf, but instead the path is ../myobject.swf.