A NetWare Btrieve application running on a server (that is, a Btrieve-based application running as an NLM) can access data on the local server or on a remote server, as follows:
The following sections describe the events that occur when a Btrieve-based application running as an NLM on a NetWare server makes local and remote requests.
When an application running on a server accesses data stored on that server, the Btrieve NLM must also be loaded on that server. The following steps describe accessing data stored on the local server:
If the Message Router is loaded, it relays the call to Btrieve on the local server.
If the Message Router is loaded, Btrieve returns the data and status code to the Message Router. The Message Router then transports the data and status code to the calling application.
When an application running on a local server accesses data stored on a remote server, both the Message Router and the Btrieve NLM must be loaded on the local server, and BSPXCOM and the Btrieve NLM must be loaded on the remote server. The following steps describe accessing data on a remote server:
The Message Router places the results in the application's memory at the location designated by the parameters passed to Btrieve in the function call. Control then returns to the calling application.