FAQs
If the Document ID is not inserted when saving new documents or versions, the integration of the macro system with your Document Management System (iManage, Worldox, etc.) must be missing or disabled.
A. If you use iManage, Word may have started without running its normal startup process, which activates the macro system integration. Close Word, make sure WINWORD.EXE is not running, then restart Word and try saving a document to see if the ID appears.
1. If it does, the problem was that Word was launched in some manner that prevented the startup process from running.
2. If it does not, please verify that the zCCCIManInt.dot template is installed and that it is not disabled. If that does not explain the problem, please contact CCC for assistance.
B. If you use Worldox, the customized version of the Worldox STARTUP template provided by CCC may have been replaced with a generic version of that template, possibly as a result of a Worldox upgrade. If you find the customized version in the WordMacroStartup folder in the main macro folder on the server, try copying that down to the local Office STARTUP folder to see if it helps. If not, please contact CCC for assistance.
C. If you use another DMS, please contact CCC for assistance.
If you receive a “SinkObject” error message when MS-Word starts, this most likely indicates one of two things:
A. That the iManage is not installed or integrated with Word. If that is the case, you must install the iManage client.
B. That the iManage client must be repaired.
C. That the specific release of the IManage client on the workstation does not match the release that was in place when the iManage integration template was provided by CCC. Please check the release number of the iManage client and compare it to the release on workstations where this error does not occur. If the error occurs on all workstations, you may have updated the iManage client. In that case, please contact CCC to arrange to update or replace the macro system integration with iManage.
A Run-time error results when a macro command attempts an invalid operation. The error gives you some information about what happened or what is wrong. However, it may not be specific enough to explain the problem.
If the Run-time error offers a clear explanation (such as a missing file), you may be able to correct the problem without any programming (i.e., by restoring the file that the macro is looking for).
In most cases, someone will need to access the programming to debug and correct the problem.
Run-time errors usually do not tell you whether the error occurred in a CCC template or a template supplied by another party, so start by asking CCC for help. If the error occurs in a non-CCC template, CCC may nevertheless be able to help, or may direct you to contact the supplier of the template.
A “Compile Error” typically indicates that a Reference in one of the global startup templates is missing or obsolete. Each of the macro templates in the startup folder – including those provided by CCC – makes references to various DLLs and object libraries that are part of Windows, MS-Office or other applications (such as DMS programs). These References allow the macros in the template to use certain commands and access certain objects made available by those DLLs or object libraries. If one of the DLL’s or object libraries is missing, or possibly if it has been updated with a new version, the Reference to it is “broken.”
What to do:
First, identify which template contains the broken reference. A compilation error should identify the module in which the broken Reference occurs:
“Compilation error in module modStyles”
If the name of the module begins with “mod” or “frm” (e.g., modStyles, frmLetter), it almost surely occurs in one of the templates supplied by CCC. If not, it almost surely occurs in a template supplied by another vendor.
If the error appears to be in a CCC module, start by asking CCC for help. If the error occurs in a non-CCC template, you may need to contact the product vendor for assistance.
To correct a missing or obsolete Reference, someone must open the macro template that generated the error, go into VBA, call up the list of References, and correct the missing or obsolete Reference by de selecting the bad Reference and selecting the appropriate replacement. CCC must do this in any CCC templates.
The following message may appear in the macro system is unable to open FirmData2010.mdb in the C:\WordMacros\WordFirmData folder:
“The macro system is unable to read the macro system database (FirmData2010.mdb). Most likely, this file has become locked. Please seek technical assistance (the Admin Guide spells out steps for correcting this problem).”
First, make sure all users have FULL RIGHTS to the WordFirmData folder.
If that is not the explanation, Windows sometimes locks this file, even though it is not in use. To address this:
1. Log in as Administrator.
2. Give the user Local Admin rights.
3. Log in as the user.
4. Go to C:\WordMacros\WordFirmdata and delete the FirmData2010.mdb file.
5. Start MS-Word, which will trigger an error because that file is missing.
6. Exit Word and run the updatemacros.bat process, to get the file back again.
7. Start Word and verify that the error disappears.
8. If desired, log back in as Administrator to remove the user’s Local Admin rights.
If clicking the M, L or F button in the ribbon produces a Runtime object error, check to see if ALN Case Profile.dot is installed in the Office STARTUP folder.
A. If ALN Case Profile.dot does appear in the STARTUP folder, rename or remove it and test to see if the errors disappear. If so, you must omit that file from the Startup folder, or reinstall Forms Workflow.
B. If ALN Case Profile.dot does not appear in the STARTUP folder, take a screen shot of – or write down – the exact error message and contact CCC for assistance.
A Run-time error results when a macro command attempts an invalid operation. The error gives you some information about what happened or what is wrong. However, it may not be specific enough to explain the problem.
If the Run-time error offers a clear explanation (such as a missing file), you may be able to correct the problem without any programming (i.e., by restoring the file that the macro is looking for).
In most cases, someone will need to access the programming to debug and correct the problem.
Run-time errors usually do not tell you whether the error occurred in a CCC template or a template supplied by another party, so start by asking CCC for help. If the error occurs in a non-CCC template, CCC may nevertheless be able to help, or may direct you to contact the supplier of the template.
A “Compile Error” typically indicates that a Reference in one of the global startup templates is missing or obsolete. Each of the macro templates in the startup folder – including those provided by CCC – makes references to various DLLs and object libraries that are part of Windows, MS-Office or other applications (such as DMS programs). These References allow the macros in the template to use certain commands and access certain objects made available by those DLLs or object libraries. If one of the DLL’s or object libraries is missing, or possibly if it has been updated with a new version, the Reference to it is “broken.”
What to do:
First, identify which template contains the broken reference. A compilation error should identify the module in which the broken Reference occurs:
“Compilation error in module modStyles”
If the name of the module begins with “mod” or “frm” (e.g., modStyles, frmLetter), it almost surely occurs in one of the templates supplied by CCC. If not, it almost surely occurs in a template supplied by another vendor.
If the error appears to be in a CCC module, start by asking CCC for help. If the error occurs in a non-CCC template, you may need to contact the product vendor for assistance.
To correct a missing or obsolete Reference, someone must open the macro template that generated the error, go into VBA, call up the list of References, and correct the missing or obsolete Reference by de selecting the bad Reference and selecting the appropriate replacement. CCC must do this in any CCC templates.
If the Master Pleading Captions or Master Service Lists buttons in the Litigation Macro Menu are disabled, there are several possible explanations:
1. If rights to these features are assigned in the Employee Data screen in FirmData2010.mdb or FirmData2013.mdb, those options may not be selected for the current user. Please check the current user’s record in the Firmdata database to verify that both these options are on. Also verify that the Network Id in the database is correct, since that is how the macros identify the user.
2. The MasterCaptions or MasterServiceLists folders may not be found. Verify that these folders are in the correct location and are accessible to the user.
3. The network macro folder may not be accessible. Verify that this folder is in the correct location and accessible to the user.
This could be a problem with the default printer driver, or the print spooler. Please open the Windows Printer list and verify that the default printer is a regular printer, not another type of device.
Also, start Word and verify that you can access the Page Setup dialog box, and the Print dialog box. If you are unable to do so, it is a printer driver or spooler issue.
If you cannot even start Word properly to perform this test, remove the zcccmacro.dotm file from the Office STARTUP folder and start Word without that template to test Page Setup and the Print dialog box. So long as Page Setup does not work in Word, the macros will not function, because they must perform a variety of actions that relate to Page Setup.
If clicking the M, L or F button in the ribbon produces a Runtime object error, check to see if ALN Case Profile.dot is installed in the Office STARTUP folder.
A. If ALN Case Profile.dot does appear in the STARTUP folder, rename or remove it and test to see if the errors disappear. If so, you must omit that file from the Startup folder, or reinstall Forms Workflow.
B. If ALN Case Profile.dot does not appear in the STARTUP folder, take a screen shot of – or write down – the exact error message and contact CCC for assistance.
If you receive a “SinkObject” error message when MS-Word starts, this most likely indicates one of two things:
A. That the iManage is not installed or integrated with Word. If that is the case, you must install the iManage client.
B. That the iManage client must be repaired.
C. That the specific release of the IManage client on the workstation does not match the release that was in place when the iManage integration template was provided by CCC. Please check the release number of the iManage client and compare it to the release on workstations where this error does not occur. If the error occurs on all workstations, you may have updated the iManage client. In that case, please contact CCC to arrange to update or replace the macro system integration with iManage.
If an error occurs when a user clicks on the “Outlook” button that appears in various macros, or when clicking on the Insert Outlook Contacts button in the ribbon, it most often indicates that the macro is encountering an error when scanning the user’s Outlook Folder List. Most likely, the user is not able to open one of the folders in their Folder List. It may be a folder in another user’s mailbox that has been added to the user’s folder list, or possibly a public folder that is displayed but to which the user no longer has access.
To determine whether this is the problem, try going through every folder in the user’s Folder List in Outlook, clicking on each one to verify that the user is able to view its contents without error. If an error occurs, that folder must be removed, or the user must be given rights to it.
If no such error occurs, please contact CCC for further assistance.
The “Create Word Doc” button appears when a contacts folder is opened in Outlook. If this button does not appear, the CCC Outlook Add-In must be installed.
In some versions of CCC Macro Pro, this Add-In is a file called CCC.DLL located in the C:\WordMacros\Outlook folder, which should be registered when you run the macro setup process.
In other versions, it is a file called CCCOutlookAddin.vsto located in the Outlook.NET_Install folder in the macro system folder on the server.
If you are unable to apply a style by selecting it from the CCC Styles menus, it means one of two things:
1. If this occurs in a specific document, the document does not contain the CCC styles. In that case, you must run the Copy Firm Styles to Document option in the Doc Cleanup menu.
2. If this occurs in a blank new document, the user has the wrong version of the Normal.dotm template. CCC provides a customized Normal.dotm that contains the @Normal and other styles. You must install this Normal.dotm from the MasterNormalDotM or WordUserTemplates folder in the macro system folder on the server, replacing the user’s current one. Running the macro setup process also would do this, but it might overwrite the user’s My Settings, as well, so it is safest to manually copy down the Normal.dotm provided by CCC.
If you create a new blank document, and the @Normal style is not present and/or is not the default style, the user has the wrong version of the Normal.dotm template. CCC provides a customized Normal.dotm that contains the @Normal and other styles. You must install this Normal.dotm from the MasterNormalDotM or WordUserTemplates folder in the macro system folder on the server, replacing the user’s current one.
Running the macro setup process also would do this, but it might overwrite the user’s My Settings, as well, so it is safest to manually copy down the Normal.dotm provided by CCC.