ITP DID Language

DID Module

You must use LOCAL for the CONNECTION attribute in a DID Module that contains Local Connection Entries. A DID can contain multiple Local Connection Modules.

Entries and fields

You must specify the attribute CALLING_CONVENTION for the Entry, so ITP knows how to call the data and key retrieval program or DLL-function for that Entry. The CALLING_CONVENTION can be PROGRAM for programs, DLL32 for 32-bit DLLs or DLL16 for 16 bit DLLs.

If the CALLING_CONVENTION is set to PROGRAM, you should specify the name of the program to call at the DATA_RETRIEVAL or KEY_RETRIEVAL attribute.

If the CALLING_CONVENTION is set to DLL32 or DLL16, you should specify the name of the function to call and the DLL in which it resides at the DATA_RETRIEVAL or KEY_RETRIEVAL attribute. This should be in following form: <functionname>@<dllname>.

Example

This is an example of (a part of) the definition of a Local Connection Entry that uses a program for data retrieval:

DEFINE_ENTRY
   NAME                     MyEntry
   MODEL_DOC_STATEMENT      WITH
   CALLING_CONVENTIONS      PROGRAM
   DATA_RETRIEVAL           "MyProg.exe"
   KEY_RETRIEVAL            "*NONE"
...

Example

This is an example of (a part of) the definition of a Local Connection Entry that uses a function in a 32-bit DLL for data retrieval:

DEFINE_ENTRY
   NAME                     MyEntry
   MODEL_DOC_STATEMENT      WITH
   CALLING_CONVENTIONS      DLL32
   DATA_RETRIEVAL           "MyEntry@MyDll.dll"
   KEY_RETRIEVAL            "*NONE"
...

Datatypes

You can use all data types for Fields in a Local Connection Entry. However, the program or DLL function must take care of conversion where applicable.