Desktop User Guides > Professional > Troubleshooting > UNICOM Intelligence Professional FAQs
UNICOM Intelligence Professional FAQs
This section provides answers to some frequently asked questions that relate specifically to working in the UNICOM Intelligence Professional IDE.
How can you make the error message go away when you are debugging?
Press Esc.
What types of files can you work with in UNICOM Intelligence Professional?
See Which file types can I work with?.
When specifying a relative path in a script, to what location should the path be relative?
When you run or debug a script, UNICOM Intelligence Professional sets the “current location” to the location of the script. This means that generally any relative paths should be specified relative to the location of the script you are running.
However, when you specify the path to an include file, it must always be specified relative to the folder in which the file that contains the Include statement is located.
When using a For Each loop with the MDM Document.Fields collection, the ScriptAssist feature does not work. Why is this?
This is because the MDM Document.Fields collection can contain objects of more than one type. For example, the Document.Fields collection can contain Variable, Class, Array, Grid, and Compound objects.
Because UNICOM Intelligence Professional cannot tell the object's type, it is not able to provide ScriptAssist. The same thing applies to any other collection that can contain objects of more than one type.
I have used the following code to create an object in UNICOM Intelligence Professional, but I can't see the type library in the Types pane. Why is this?
Dim MyComponent
MyComponent = CreateObject("MRDSCReg.Components")
When you assign objects in mrScriptBasic, you need to use the Set keyword. So to make the type library appear in the Types pane you need to change your script as follows:
Dim MyComponent
Set MyComponent = CreateObject("MRDSCReg.Components")
Then reference the object and type the dot (.) that activates the ScriptAssist feature. Now the type library will appear in the Types pane.
I have rearranged the various panes in the UNICOM Intelligence Professional IDE. How can I return them to their original positions?
See Changing the window layout on page 16 for more information.
Is there a way for me to add my own object model so that I can get ScriptAssist on it?
UNICOM Intelligence Professional automatically makes ScriptAssist available for all suitable COM object models that are created using the CreateObject function. However, ScriptAssist is not available if the object model is based on IDispatch interfaces only, because then the necessary type information is not available.
Is ScriptAssist available for mrScriptMetadata?
No, ScriptAssist is not available for mrScriptMetadata.
Why does a line feed appear as a small square in the Locals pane?
The square symbol is used to indicate a line feed, because the Locals pane can show only one line for each variable.
How does the Locals pane show variables that are declared within a function or subprocedure?
The Locals pane follows the mrScriptBasic scope rules and displays local variables only when in the function or subprocedure.
When I open an existing script, change it, and then close it without running it, I am asked whether I want to save my changes. However, I am not asked this if I run the script before closing it. Why is this?
This is because you have the Save Before Execution option set to True. This option means that scripts are automatically saved before you run them. If you want UNICOM Intelligence Professional to always ask whether you want to save the script before running it, set this option to False. See UNICOM Intelligence Professional options for more information.
Is there a way of viewing a variable's label in the Metadata Viewer, like you can in MDM Explorer? I need to see the labels in order to distinguish between the various variables, some of which have similar names.
You need to show the Properties pane. You do this by choosing Properties from the View menu. Then, when you select a variable (or category) in the Metadata Viewer, the Properties pane will show the properties of the variable (or category), a bit like the right side of the window in MDM Explorer does. If you scroll down through the properties, you will come to the label.
Why do I get the message “The selected Font is not supported in UNICOM Intelligence Professional. UNICOM Intelligence Professional will revert to the previously used Font” when I try to change the default UNICOM Intelligence Professional font?
The font that you have selected does not meet the requirements for IUNICOM Intelligence Professional. The default requirement for an UNICOM Intelligence Professional font is that it must support bold and italic. To add or remove font requirements, edit the UNICOM Intelligence Professional syntax definition files.
When I closed and reopened my new interview script (.mdd) file, I noticed that the layout of the code in the metadata section has changed. Why has this happened?
This is because the language used in the metadata section, mrScriptMetadata, contains its own internal instructions that determine how the syntax of the language is displayed. This is designed to make mrScriptMetadata easier to read, for example, by defining a single question over several lines rather than on one long line.
When I start UNICOM Intelligence Professional, a message appears telling me that my license has expired. How do I renew my license?
Run C:\Documents and Settings\All Users\Application Data\IBM\SPSS\DataCollection\7\Professional\\licrenew.exe and when prompted, enter the new license code(s) that have been supplied to you.
Why do I receive a message that says required variables are missing and reactivation is required when I attempt to open an MDD in UNICOM Intelligence Interviewer 7.0.1?
UNICOM Intelligence Interviewer supports new system variables in the 7.0.1 release. If an MDD file does not include these system variables, reactivation to UNICOM Intelligence Interviewer 7.0.1 is required. See Activating interview scripts for more information.
See also
Error messages
Data Management troubleshooting