Can compile OCX in db1 but not in db2 on same computer

superbruger
superbruger Member Posts: 41
edited 2011-06-17 in Navision Financials
I have a codeunit where I use Microsoft Common Dialog Control, version 6.0 and I can compile it and use it.

When I import this codeunit to another database on the same computer I cannot compile it.

Then it ask for a "design license".

(I'm not sure the codeunit in db1 was originaly designed in this db)

What can I do to compile this on db2 ?

Comments

  • superbruger
    superbruger Member Posts: 41
    I installed the Developer Kit for MS Office and then it worked. Strange that I could compile in one db and not in the 2. But now I can....
  • Tommy_Schou
    Tommy_Schou Member Posts: 117
    True. That is rather weird. But I have the exact same experience.

    Did you by chance import the object as a .txt-file and not as a .fob-file? In my experience it makes a difference. If it is via a .fob-file you should be able to compile it. If it is as a .txt-file you will get the error with regards to a license for the ocx.
    Best regards
    Tommy
  • mxi
    mxi Member Posts: 9
    Hi,

    in my case I get the error with the design license, if I import the object as txt on our server (Windows 7 64 bit) and try to compily directly on the server(via remote desktop).
    If I compile the object from my local computer, it works fine.
    The ocx is registerd on the server in folder syswow64, but it doesn't work.
    Only an import via FOB works on the server.

    If anybody knows another ocx especially for Windows 7 64bit or another way to solve this porblem please let me know.

Categories