2.0

The OLE DLL name.

extern "C" short WINAPI VCGetOleDllName(short* iError, char* szPath);
extern "C" void WINAPI VCSetOleDllName(short* iError, char* szPath);

function VCGetOleDllName(var iError: Smallint; szPath: PAnsiChar):Smallint; stdcall;
procedure VCSetOleDllClassName(var iError: Smallint; szPath: PAnsiChar); stdcall;

Function GetOleDllName() As String
Sub SetOleDllName(ByVal szPath As String)

szPath - the OLE DLL name.
Return - the length of the returned string.

Visual CADD™ can run functions from within a DLL through the scripting language. This allows developers to create add on applications in a Windows DLL format and then simply reference functions contained in the DLL. Visual CADD™ will load the DLL into memory and access the specified function. Generally, this is simply done through the Visual CADD™ interface with the Assign Script command or the CMDEXT file. Please refer to Customizing Visual CADD™ for more information this. An application can also launch the routines through the API.

In order to access the DLL function, Visual CADD™ must know the DLL name, the name of the function and any command line arguments required. The command line arguments can only be passed as a character string. The engine then uses this information to launch the specified function.

OLE DLL are special cases of the standard DLL method. OLE DLL are created as exported class routines. Visual CADD™ must handle this differently when accessing the functionality built into the DLL. This information is provided by an OLE DLL name, a class name containing the function, the function name and the command line argument for the function.

VCGetDllRunCmdLine, VCGetDllRunFunction, VCGetDllRunName, VCGetOleDllClassName, VCGetOleDllFunctionCmdLine, VCGetOleDllFunctionName