Share via

Checklist [Office 2003 SDK Documentation]

  • Article

Following is a checklist that you can use if you are unable to view the smart document controls in the Document Actions task pane, if you receive an error message that smart document logic is missing or invalid, or if your smart document doesn't function as expected, either in part or as a whole. For more information, see Troubleshooting Common Problems.

  • Spell the XML element names specified for the type constants in the code exactly as they are spelled in the schema, including case.

  • Spell the XML namespace specified for the namespace constant in the code exactly as it is in the schema, including case.

  • Match the <uri> element in the XML expansion pack manifest file to the schema namespace, or the smart document will fail to load.

  • When you specify the ControlID property, make sure you reference the correct control ID number when referencing that control elsewhere in the code. For example, if you specify that the controls for an element use the value of "ControlID + 200" and there are five controls for that element, you should use the ControlID value of 204 if you want to access the fourth control in the element. For more information about how to do this, see the tutorials or the ControlID property.

  • Verify that the solution is attached to the document. For more information, see Attaching an XML Expansion Pack.

  • To run unsigned components during testing, set your application security level to Medium, with the Trust all installed add-ins and templates check box cleared. This way Microsoft Office 2003 will prompt you to either enable or disable add-ins and macros.

    Alternatively, you can also sign your component using a test certificate. In this case, you can keep your security setting at High, with the Trust all installed add-ins and templates check box cleared.  And if you add the test certificate you created to the trusted sources list, you will not be prompted thereafter to enable or disable a component that was signed using that particular certificate. For more information, see Digital Code Signing for Testing Purposes.

  • If you have a managed smart document, verify that you included the managed element in the XML expansion pack manifest file.

  • If you have a managed smart document, make sure you included any interop assembly files for COM components with the other files included with your smart document, and verify that you added a file element for the interop assembly in the XML expansion pack manifest file. For more information, see Security for Smart Documents That Use the .NET Framework.