License File Problems (COM Version)

All those licenced to develop applications using DicomObjects (as opposed to merely running applications) should have a file called DicomObjects.Lic which must be in the same directory as the active copy of DicomObjects.ocx. There are many reasons why developers sometime find that they get a message telling them that that the license is not available, and therefore that they do not have permission to use the objects in a design environment.

Downloading a Trial Version

The Trial version of DicomObjects is a completely separate version, so if you are a licenced developer you should not attempt to upgrade by downloading a trial version. Instead, you should ask us (support@medicalconnections.co.uk) for a full version instead.

If this is the problem:

  • You will get a trial expiration warning
  • You need to de-install the trial copy
  • Then you download and register (using RegSvr32) a new full version from the developer web site

Accidentally changing the location of your active DicomObjects.ocx file

The most common cause for this is testing out an installation routine, made using InstallShield etc. for your finished product on the development machine. When this is done, if DicomObjects is part of the install, then a new copy of DicomObjects.ocx will be made, and put somewhere different (commonly C:\Windows\System32), and of course that copy does not have a copy of DicomOBjects.lic with it. Of course, a tempting solution is to put DicomObjects.Lic into the installation package, but this is specifically forbidden, as it would break the licencing rules and controls for DicomObjects. There are a few solutions:

  • Accept that as the new location
This is easy to do, and only requires that you copy DicomObjects.lic manually into the same location as DicomObjects.ocx
  • Revert to your original location
    This is a little harder as there is a bug (feature?) in Microsoft Installer such that you cannot simply revert to using your original location by using RegSvr32 as (though it will appear successful) it will fail as long as the new copy (which gets a sort of priority) still exists, so you must either:
    • De-install your own application from the Control Panel
      or
    • Delete the new copy of DicomObjects.ocx before using RegSvr32 to revert to the original location
Relevance: