Actionscript error message

Question

Using Captivate 6. When trying to publish a file for proofing, with eLearning output disabled, I receive this error message: Swf compilation failed. Note: Please verify if any of the actionscript keywords is used as user variable name. Where should I look to try to solve this issue?

Answer 1

Some info copied and pasted from my e-book on Troubleshooting Captivate 6:
Reserved keyword error
Solution 1: Try hiding slides and republishing
I struck this error once after adding a Certificate widget at the end of a Captivate 6 project.  Thinking that the issue was the widget, I hid the widget slide and republished the project successfully.  Then I unhid the widget slide and published again successfully.  So whatever caused the glitch during the first publish had resolved itself just by hiding the last slide added.  Perhaps you will be so lucky.  As stated in our section about troubleshooting tips, always try the easy solutions first.
Solution 2: Avoid using punctuation in fields
This error can result if you have inadvertently added punctuation marks in object Item Names, slide labels, project information fields, etc. Certain characters (such as [ ] / “ ‘ # : ; etc) are also used in programming languages and Captivate may mistake these characters for executable code.  If you experience this error, the solution requires searching through all data fields in your project file to remove any punctuation characters you find in the following field areas:
Project information
Slide labels
LMS settings
Quizzing labels
Closed captioning text
Slide notes text
Solution 3: Copy/paste objects to reset object identifiers
Another possible reason for this error can be that you’ve been copying and pasting content objects or slides from one project to another and this has somehow created a conflict because two objects ended up with the same unique identifier in the project file.  They start fighting over who gets the honor of keeping the name and Captivate falls over as a casualty of war.  Fortunately, this issue is now quite rare because Adobe has progressively built more safeguards into Captivate to prevent these conflicts.
Paradoxically, the solution is to do yet another copy / paste run, but this time paste into a new blank project of the same size with no other slides or objects.  The reason this method works is that when Captivate objects are copied and pasted they are always assigned new unique IDs, even when you copy and paste into another slide of the same project.  So if the issue is due to a conflict between items with the same identifier, copying all slides and objects into a new project file forces Captivate to reassign new IDs, which then ensures they are all unique again.
The downside of this particular method is that copying and pasting to another project will NOT retain any Advanced Actions or Variables that you had set up in the original project.  So you may need to set those up again.