5.3.5 Set Up API and Macro Security Dialog Box

From this dialog box, you can enable the InfoConnect .NET API, and specify corresponding settings.

NOTE:If you need to use the API in multiple instances of InfoConnect simultaneously, use layouts. You can specify different settings for the IPC channel name for each layout in the Layout Settings dialog box.

API Settings*

Disable API

Select to prevent custom applications from accessing this installation of InfoConnect.

Legacy API preference

Use this setting to determine if InfoConnect legacy macros are supported, and to determine which legacy API has preference for the GetObject() method used to retrieve API COM objects. InfoConnect supports multiple APIs, but can accept GetObject() calls for only one type of legacy API object at a time.



If you


No Legacy API

Don't use legacy macros, or if your code doesn't use GetObject() to access legacy API COM objects.



Use legacy Reflection macros, or if you use GetObject() to access legacy InfoConnect API COM objects. Each session document that you subsequently open or create has legacy macro capability; it includes a legacy VBA project in addition to the standard VBA project in the Visual Basic Editor.

NOTE:Legacy API support is provided in all InfoConnect settings files that you open in the workspace (including settings files saved as InfoConnect session documents), regardless of this setting.



Use GetObject() to access Extra! API COM objects.

Action Permissions

Specify what you want to happen if an action that has been restricted through Group Policy or the Permissions Manager is initiated through a macro or API call.

Require elevated rights

Select to control restricted actions with User Account Control (UAC).

Execute the action

Select to run restricted actions that are initiated through a macro or API call as expected. The same actions won't run if they are initiated through the user interface.