EAServer’s ActiveX client model allows you to invoke EAServer components from ActiveX enabled IDEs such as Visual Basic.
To develop and run ActiveX clients, you need:
A supported client operating system such as Windows NT 4.0 or Windows 2000. The ActiveX client can call server components executing on any any platform. See the EAServer Installation Guide for Windows for more information on operating system requirements.
C++ client and ActiveX runtime files, which includes jagproxy.dll, the required .tlb and .reg files, and the C++ DLLs required for use with an ActiveX CORBA client. See the EAServer Installation Guide for Windows for instructions on installing the client runtime.
An ActiveX-enabled IDE. The following list includes some of the ActiveX-enabled IDEs you can use:
Visual Basic 4.0 or later
Visual C++ 4.0 or later
Type libraries (you generate these files using EAServer Manager).
Registry files (you generate these files using EAServer Manager).
The Microsoft tool uuidgen.exe, which is provided with EAServer on Windows, must be installed on the server. The Microsoft tool midl.exe must be installed on your client machine and specified in the path. midl.exe must support the /tlb command-line option. You can issue this command to see the options that your midl.exe version supports:
midl /?
midl.exe is distributed by Microsoft as part of their development tools and as part of the Win32 SDK. Many tools from other vendors include a redistribution of the Win32 SDK. Visual C++ 4.2 or higher contain the correct version of midl.exe. You can also download midl.exe from the Microsoft Developer Network web site.
Make sure that an older version of midl.exe is
not located in a directory that is specified prior to the current midl.exe directory
in the PATH environment variable.
EAServer Manager on Windows NT or Windows 2000.
See the EAServer Installation Guide for
Windows for additional system requirements.
