Type "Automation" not available in Locals

dstiegele
dstiegele Member Posts: 10
edited 2004-04-06 in Navision Attain
Hi,
why can't I use a variable-type "Automation" because it is not available in the Drop-Down-field in the locals (of a form e.g.)?
Our Navision solution-center told me, that a not present licence (1750-ocx) could not be the reason because they can insert a variable with our license and it seems to work.
Are there any other reasons like special office-installation-parts or os-requirements?

Thanks in advance!

Dirk Stiegele

Comments

  • wonmo
    wonmo Member Posts: 139
    You do NEED the OCX license. How your solution provider is able to create automation variables with your license even though it doesn't contain this granule is a complete mystery.
  • dstiegele
    dstiegele Member Posts: 10
    Meanwhile I got the answer that they tried it with the exchange of the local flf-file but with their own systembuilder-license on the server ;-)

    So it looks like we need another licence......

    Thank you, wonmo!

    Best regards
    Dirk Stiegele
  • wonmo
    wonmo Member Posts: 139
    You're welcome Dirk.
    I highly recommend getting this granule. If something can't be done within Navision you can almost always come up with a solution using the automation and ocx variable types. Sometimes, though, it may take a bit of work (like importing data from 50 tables within an Access database using ADO, creating a route planner/mapper using Mappoint as an automation server and then e-mailing it automatically to a recipient, etc.).
  • Mark_Tsirik
    Mark_Tsirik Member Posts: 1
    curiously, but yesterday I have experienced exactly this problem - a variable-type "Automation" was not in the Drop-Down-field list on a test database.
    In my case the problem was that there was no any login defined in this database. After I have a super-user login created, the "anomaly" has disappeared.
  • kine
    kine Member Posts: 12,562
    dstiegele wrote:
    Our Navision solution-center told me, that a not present licence (1750-ocx) could not be the reason because they can insert a variable with our license and it seems to work.

    When you haven't granule 1750, you have no Automation or OCX option in drop-down menu for variable type. But you can still use all objects, which uses OCX or Automations... When your NSC use their licence for adding some OCX or Automations, you can still use this objects, but without gr. 1750 you can't add new variables of OCX or Automation type...
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • dstiegele
    dstiegele Member Posts: 10
    Yes, it was the granule 1750.
    After getting this license all autoamtion servers are available.

    But the documentation (word-connection) is not very good. Does anybody know a good source for help?

    Thanks.

    Dirk

Categories