Linkar CLIENT libraries are used to create client interfaces to servers. Programmers use a variety of functions to request and receive data, and to execute programs in database applications. Using Linkar CLIENT libraries has these advantages compared other connectivity options:
- For security and other reason, the client app does not interact directly with the database. The application communicates with Linkar SERVER, and Linkar SERVER interacts with databases.
- Your applications do not need different libraries, depending on the MV databases being used. One set of client code will support multiple MV server types.
- There are several Linkar CLIENT language bindings, allowing developers to use consistent client-side development patterns to access servers.
Linkar CLIENT components are available for use with different programming languages and environments:
- NET (C#, Visual Basic, F#,...) for Windows x64 and x86 environments.
- MONO for multi-platform development (Linux, Mac,...).
- Java (all OS types).
- All languages and environments which can use C Libraries, such as PHP, Python and NodeJS
- COM-compliant languages like Excel VBA and PHP.
- A console application, in order to make operations from, for example a command script from the OS.
- From BASIC to another remote Database, regardless of which is it.
- Linkar comes with a console application, embedding Linkar CLIENT, to perform operations from the OS command-line and scripts. For example, you can write a .bat file or shell script that sends and retrieves data to/from the MV server for any purpose.
This example shows how to create a simple application in C#.
LINKAR Libraries and Platforms from where they can be used:
|LinkarClient.dll ||.NET Framework Client |
|LinkarClientCOM.dll ||Languages compatibles COM (php, office VBA, ...) |
|LinkarClientMono.dll ||Mono Framework Client (Windows, Linux, Mac) |
|LinkarClientCore.dll ||.NET Core (Windows, Linux, Mac) |
|LinkarClient.jar ||Java Client |
|LinkarClientC.dll / LinkarClientC.lib ||C libraries for Windows |
|libLinkarClientC.so / libLinkarClientC.a ||C libraries for Linux |
Linkar has four types of Functions:
Are exclusive of the OOP (OBJECT-ORIENTED PROGRAMMING) and allow the creation of a LinkarClt object that manages all the operations.
After creating the object it is necessary to make a Login that through a Session code allows making all the wished operations until a call to the Close method is produced or until the session expires because of inactivity, defined on its EntryPoint.
They are useful for applications that require user identification, for instance to log into an ERP session.
Used for the direct and independent communication with the Database. Its arguments contain the necessary information to identify the user before returning the required information. Unlike the Persistent Functions these don't have Session Code, each call is completely independent from the others and do not have Login or Close functions.
They are used for Database access from public webpages, for instance online shops.
These type of function doesn’t need to access the Database. They are executed in the client and its goal is to ease the management of the MV buffers.
C AUXILIARY FUNCTIONS
Are C libraries exclusive
They are executed in the client and its goal is to allow an easier management of other complex C functions.
There are no classes in C, nor objects also, these functions are used to create encoded strings that emulate other languages.
On the other hand, LINKAR supplies other types of calls:
They are executed in the same thread of the main application, so they block the execution of the application until they finish.
They are executed in a different thread, so they don't block the execution of the application. When the call is made a return method is required (Callback) which triggers when finished the operation.