Working with existing Export components
When you create a new export component using the UNICOM Intelligence Reporter - Survey Tabulation Export Wizard, it might be helpful to refer to one of the existing export components that are included with UNICOM Intelligence Reporter - Survey Tabulation. Alternatively, you can change the export script from an existing export component to tailor it to your requirements.
You can use the Microsoft Visual Studio .NET resource editor to export the script from an export component's .dll file, and then refer to it or edit it as required.
In the default installation of the UNICOM Intelligence Reporter, the export components are located in C:\Program Files\Common Files\IBM\SPSS\DataCollection\7\ TOM. If you do not have the UNICOM Intelligence Reporter installed, and you are using the browser-based UNICOM Intelligence Reporter - Survey Tabulation, you can unpack the .dll from the .cab file of the export component that is located on the UNICOM Intelligence Interviewer - Server Admin server. Or, the .dll file for any export you've previously downloaded will already be unpacked and installed in the default location of C:\Program Files\Common Files\IBM\SPSS\DataCollection\7\TOM.
The export components are 32-bit, even if you install the x64 64-bit version of UNICOM Intelligence Reporter - Survey Tabulation.
To change an existing Export component
1 Create a working copy of the .dll file of the export component that you are interested in (for example, ExportText.dll). This will prevent accidental permanent changes to the existing export component.
2 In Microsoft Visual Studio .NET 7.0 or 2003, click File > Open > File.
3 Open the working copy of the .dll file that you created. The .dll file is displayed in Visual Studio as a list of resources.
4 Expand the “SCRIPT” resource to see the script file. In ExportText.dll, it is called 105.
5 Right-click the script file, and then click Export.
6 In the File Name field, change the file extension to that used by the script language (.vbs or .js) and click Save to export the contents to a script file. The resource is easier to edit as a script than as a binary resource file.
You cannot change the script language of an existing export component. If the original script was written in VBScript, you must replace it with VBScript. The supplied export components use the following script languages:
▪Excel Export uses VBA macros; these are listed as “SCRIPT” resources 106 and 107. Save the files with a .vbs extension to edit them.
▪The PowerPoint Export and Text Export scripts use VBScript.
▪The Microsoft Word Export script uses a number of Word macros; these are listed under the “WORDMACRO” resource. Save the files with a .vbs extension to edit them. This script also includes a Word template file; this is listed under the “WORDTEMPLATE” resource (228), and you can edit it in Word by saving it with a (.dot) extension.
7 Open the script file in Visual Studio or other editor, and then edit it.
8 Copy the text of your edited script file to the clipboard.
9 Open the export .dll window in Visual Studio, and then double-click the “SCRIPT” or “WORDMACRO” resource to open it in the binary resource editor.
10 Replace the text with the changed script from the clipboard (Ctrl+V).
11 Save all files.
12 Replace the .dll in the TOM folder with your edited version to deploy the changed export component on your own computer.
See also