Category Archives: FAQ

“The program can´t start because mfc120d.dll is missing “

This problem has been described in a previous post. The recommended installation of the Microsoft redistributable package does not seem to solve the problem in every case.

We have made the missing DLLs available on our website. You can download the files here and copy them to your SCOUT or CODE program folder directly, without executing any installation routine.

The relevant program folders are (very likely) c:\scout\ (in the case of SCOUT) or c:\code\ (for the CODE software).

Bugfix master model

With version 4.56 we have removed a bug in master models for optical constants. Saving a successful model and re-loading it could lead to a strange mix-up of parameter values in some situations, leaving the poor user with a useless configuration. We recently taught CODE and SCOUT to correctly count master and slave parameters – saving and loading should work now.

MSVCP120.DLL is missing …

If you try to run CODE, SCOUT or SPRAY with object generation 4.50 or higher and you get this message please install the Visual C++ Redistributable package for Visual Studio 2013. Here is the link:

https://www.microsoft.com/en-us/download/details.aspx?id=40784

If you follow the ‘Download’ section you have to select the vcredist_x86.exe. Running this will install the required DLL files.

Batch import using Excel files

If you have used the option to export measured spectra in CODE using Excel format you can now import these spectra in batch mode.

There is a restriction, however: The spectra must be stored in the first worksheet of the Excel document, with the first wavelength in cell A1.

The number of the file format to be used in the batch control sheet is 27.

This feature is available starting with object generation 4.48.

 

OLE server only

When I try to start the software I get the message: ‘This program can be used as OLE server only!’. What does that mean?

The program has been installed with a passport file which allows to run the program as OLE server only. It cannot be started as a normal desktop application.

Very likely you have downloaded the software from our website and installed it on your system. The download packages do not contain valid passport files, i.e. valid user licences. After the installation, you have to copy a valid passport file into the program directory.
In the case of SCOUT, the passport file is called scout_passport.wtp. If you installed CODE the name is code_passport.wtp.

In the case of a software purchase you should have received a passport file from us either by e-mail or with the setup CD. If you are evaluating the software you should have received a passport file with a demo licence by e-mail.

Can’t create object

I try to use CODE in VisualBasic but I get the error message ‘ActiveX can’t create the object’?

First check if the name of the OLE automation server in the VisualBasic command is correct. The server name of CODE is ‘code.colors’.

If this does not solve the problem, the registration of the OLE automation server is probably incorrect for some reason. When you run the setup program, CODE is registered as OLE automation server automatically. If this action failed, a call of the server in VisualBasic does not work. In this case you can do the registration manually.
Start a Windows command line by clicking on the Windows key on your keyboard followed by the letter ‘r’ (for run). You must have administrator rights to do registrations. If you are logged-in as a normal user, you can right-click the command line in ‘Start/accessories’ and select the option ‘Run as administrator’. Once the command line is available, type in the command
“c:\program files\code.exe” /regserver
where you should make sure that you use the double quotes as shown. The path of the program file code.exe must be adapted to your system, of course, i.e. it should point to the location of your code program.
If you work with different CODE versions on one computer, you might want to use the command
“c:\another_installation_folder\code.exe” /unregserver
in order to explicitly de-register a code program as OLE server.

Difference spectra

How can I display the difference of simulated and measured spectra?

Sometimes it is advantageous to inspect the difference of simulated and measured spectra in order to find out about appropriate model extensions. Please read the instructions below to activate the drawing of difference spectra.

Open the spectrum for which you want to see the difference with a right-click in the treeview. Select the local menu command File/Options/Difference/Show to turn on the difference display. This menu item is a checked property: Clicking on it changes its status from checked to unchecked or vice-versa.

The additional menu commands File/Options/Difference/Pen and File/Options/Difference/Line mode are used to control the appearance of the difference curve. Use these settings to clearly separate the difference curve from the simulated and measured spectra. You can use, for example, pen 3 (green by default) and line mode 3 (dashed).

No import routine

There is no import routine for my spectra. How can I get my data into the software?

If there is not import routine for your type of spectra, you should check first if your spectrometer system can export the spectra in a format which is recognized by our software. Most spectrometer packages can generate tables of the measured data in ASCII format which can be imported using the ‘xy-format’.

In desperate cases you can ask us to write an import routine for your type of spectra. We can do this if we get a description of the data format, and if it can be done with a reasonable amount of effort.