Set of Libraries that allow the communication of an application with the Linkar SERVER and through it with the different databases. The programmer can request and receive the information needed by the application through its functions.
Depending on the selected programming environment or the language used, the application communicates with the Linkar SERVER through the different Client Libraries and then the application accesses the databases.
Your applications do not need different versions depending on the MV database with which you are going to work with. They communicate with the Linkar SERVER and this is responsible for everything that is necessary.
There are Linkar CLIENT versions compatible with different programming languages and environments:
- NET (C#, Visual Basic, F#,...) for Windows x64 and x86 environments.
- CORE and MONO for multi-platform development (Linux, Mac,...).
- Java (all OS types).
- All languages and environments that can use C Libraries, such as PHP, Python and NodeJS.
- COM-compliant languages like Excel VBA and PHP (windows).
- A console application, so as to carry out operations from it, for example a command script from the OS.
- From BASIC to another remote database, regardless of which this is.
- 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.
- Linkar also includes an MV-side client to connect with other MV servers that can read, write, or execute commands on a remote system, even with a different MVDBMS type.
This Video Shows how to create a simple appication in C#
LINKAR Libraries and Platforms from where they can be used:
||.NET Framework Client
||Languages compatibles COM (php, office VBA, ...)
||Mono Framework Client (Windows, Linux, Mac)
||.NET Core (Windows, Linux, Mac)
|LinkarClientC.dll / LinkarClientC.lib
||C libraries for Windows
|libLinkarClientC.so / libLinkarClientC.a
||C libraries for Linux
Linkar can use four types of Functions:
Exclusively from 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 Login that, through a Session code; this allows it to make all the desired operations until a call to the Close method is produced or until the session expires because of inactivity. This is defined on its EntryPoint.
They are useful for applications that require user identification, for instance, to log into an ERP session.
Used for direct and independent communication with the database. Its arguments contain the necessary information to identify the user before returning the required information. Unlike persistent functions, these do not have a Session Code, each call is completely independent of the others and does not have Login or Close functions.
They are used for database access from public websites, for instance online shops.
This type of function does not need to access the database. They are executed in the client and their goal is to ease the management of the MV buffers.
C AUXILIARY FUNCTIONS
C auxiliary Functions are exclusive for C libraries.
They are executed in the client and their goal is to allow easier management of other complex C functions.
There are no classes in C, or objects , these functions are used to create encoded strings that emulate other languages.
Linkar also 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 new thread, so they do not block the execution of the application. A return method is required when a call is made (Callback) which is triggered when the operation is completed. C libraries do not implement this type of calls.