We changed the Templates so that all of the Source Code is available in the Embeds. This way if you need to change the functionality of a Template Procedure, you no longer have to Edit the Template file. You can simply change the Embedded source code.
If you receive Compile Errors after Upgrading to a new version of CLACom, you should UnRegister the CLACom Template, ReRegister it, and if you still receive compile errors, perform the following steps:
If you are utilizing them, delete the PhoneMonitor, DialNumber and InitializePort Procedures. They will become "todo" Procedures.
Once removed, you can then add the Template Procedures back in to your Application.
There are two developer files, in addition to the CLACom32.DLL, that must remain synchronized. These are:
- clacom.inc
- clacom32.lib
- clacom32.dll
If one or the other is out of sync, you will receive linker errors. Whenever you download a new version or restore from a backup, be sure that you reference the 3 files from the same release. For instance a version 6.0 clacom.inc will not work with a version 6.1 clacom32.lib.
Applications that utilize CLACom must include two files (Function Prototypes and Global Variable declarations) as well as one Import Library. The Example programs include these files, however the paths are relative to our Development Directory. You will need to fix the Path to the 2 Include Files and the Import Library.
In the Global Application Embeds, select "Inside the Global Map", and change the path to the CLACOM.INC file so that the file can be found during compile time. Do the same for the CLACOMST.INC file in the "Global Data" Embed.
You will also need to edit the Project, delete the CLACom Import Library (CLACOMxx.LIB) and then add it back in so that the Clarion Linker knows where to find it.
