Abstract: Methods and apparatus for scrolling database records, particularly in a client-server computing system, are disclosed. A database holds records, accessible by a server, that each include a unique identifier. A client requests the server to retrieve a set of database records. Records are retrieved from the database and stored on the server. The server determines an upper context token and a lower context token corresponding to the end records for a subset of those records. The upper and lower context tokens include a reference to the respective unique identifier. The first subset records is passed to the client for display. The client then makes a scrolling request by a previous or next subset of data, and passes the relevant upper or lower context token to the server.

Abstract: Methods and apparatus for scrolling database records, particularly in a client-server computing system, are disclosed. A database (104) holds records, accessible by a server (102), that each include a unique identifier. A client (100) requests the server (102) to retrieve a set of database records. Records are retrieved from the database (104) and stored on the server (102) The server determines an upper context token and a lower context token corresponding to the end records for a subset of those records. The upper and lower context tokens include a reference to the respective unique identifier. The first subset records is passed to the client for display. The client then makes a scrolling request by a previous or next subset of data, and passes the relevant upper or lower context token to the server.

Abstract: Methods and apparatus at servicing-linked applications in a client-server environment are disclosed. A client 20 is in communication with a server 30, and both are running a main application (in one form a goods and services ordering application). An associated application (for example, On-Line Help) is supported by a second server 30′. When OLH is invoiced on the client 20, a unique identifier is passed to the main application server 30, which locates a corresponding URL string and passes the string to a browser 130 on the client 20. The browser 130 passes the URL to the OHL server 30′ where the respective OLH document is retrieved from a datastore 40, and returned to the client 20 for display on the screen 100.