Difference between revisions of "RPC HELP DLL Introduction"
(Created page with " RPC Broker Help Home RPC Broker 32-bit DLL Interface Introduction The functionality of the TRPCBroker component for Delphi is provided in a 32-bit Dynami...") |
|||
Line 1: | Line 1: | ||
[[RPC_Broker_Help| RPC Broker Help Home]] | [[RPC_Broker_Help| RPC Broker Help Home]] | ||
− | RPC Broker 32-bit DLL Interface Introduction | + | |
− | + | [[RPC_HELP_Other_DLL_Interface_List|DLL Interface Home]] | |
+ | <h2>RPC Broker 32-bit DLL Interface Introduction</h2> | ||
+ | <h3>Introduction</h3> | ||
+ | The functionality of the TRPCBroker component for Delphi is provided in a 32-bit Dynamic Link Library (DLL) interface, in BAPI32.DLL. This enables the use of any development product that can access Windows 32-bit DLLs to create applications that communicate with VistA M Servers through the RPC Broker. | ||
In Delphi, you have direct access to the TRPCBroker component itself, and its properties and methods. In other development environments, you can only access the properties and methods of the TRPCBroker component through DLL functions. So to understand the DLL interface, you should understand how the TRPCBroker component is used in its native environment (Delphi). | In Delphi, you have direct access to the TRPCBroker component itself, and its properties and methods. In other development environments, you can only access the properties and methods of the TRPCBroker component through DLL functions. So to understand the DLL interface, you should understand how the TRPCBroker component is used in its native environment (Delphi). | ||
− | + | * DLL Exported Functions | |
− | |||
The following special issues should be considered when accessing RPC Broker functionality through its DLL: | The following special issues should be considered when accessing RPC Broker functionality through its DLL: | ||
− | + | * [[RPC_HELP_DLL_SI_RPC_Results|RPC Results for DLL Calls]] | |
− | GetServerInfo Function and the DLL | + | * [[RPC_HELP_DLL_SI_GetServerInfo_Fn|GetServerInfo Function and the DLL Calls]] |
− | + | <h3>Header Files<h3> | |
− | Header Files | ||
− | |||
Header files for using the DLL are provided for C (BAPI32.H), C++ (BAPI32.HPP), and Visual Basic (BAPI32.BAS). | Header files for using the DLL are provided for C (BAPI32.H), C++ (BAPI32.HPP), and Visual Basic (BAPI32.BAS). | ||
− | + | * [[RPC_HELP_DLL_GuideLines_CPP_Overview|Guidelines for Calling DLL from C++]] | |
− | Guidelines for Calling DLL from C | + | * [[RPC_HELP_DLL_GuideLines_C_Overview|Guidelines for Calling DLL from C]] |
− | Guidelines for Calling DLL from Visual Basic | + | * [[RPC_HELP_DLL_GuideLines_VB_Overview|Guidelines for Calling DLL from Visual Basic]] |
− | + | <h3>Sample DLL Application</h3> | |
− | Sample DLL Application | ||
The VB5EGCHO sample application, distributed with the Broker Development Kit (BDK), demonstrates use of the RPC Broker 32-bit DLL from Microsoft Visual Basic. The source code is located in the ..\BDK32\Samples\Vb5Egcho directory. | The VB5EGCHO sample application, distributed with the Broker Development Kit (BDK), demonstrates use of the RPC Broker 32-bit DLL from Microsoft Visual Basic. The source code is located in the ..\BDK32\Samples\Vb5Egcho directory. |
Revision as of 11:47, 7 July 2015
RPC Broker 32-bit DLL Interface Introduction
Introduction
The functionality of the TRPCBroker component for Delphi is provided in a 32-bit Dynamic Link Library (DLL) interface, in BAPI32.DLL. This enables the use of any development product that can access Windows 32-bit DLLs to create applications that communicate with VistA M Servers through the RPC Broker.
In Delphi, you have direct access to the TRPCBroker component itself, and its properties and methods. In other development environments, you can only access the properties and methods of the TRPCBroker component through DLL functions. So to understand the DLL interface, you should understand how the TRPCBroker component is used in its native environment (Delphi).
- DLL Exported Functions
The following special issues should be considered when accessing RPC Broker functionality through its DLL:
Header Files<h3> Header files for using the DLL are provided for C (BAPI32.H), C++ (BAPI32.HPP), and Visual Basic (BAPI32.BAS). <h3>Sample DLL Application
The VB5EGCHO sample application, distributed with the Broker Development Kit (BDK), demonstrates use of the RPC Broker 32-bit DLL from Microsoft Visual Basic. The source code is located in the ..\BDK32\Samples\Vb5Egcho directory.