Back to website >

Manage Clients

This section describes the options for managing clients from client creation to deletion.

Creating Clients

A new client is created in the start menu of EULANDA® via the right mouse menu. The dialogs are the same as for the first start and were already covered in the installation chapter, for an update additionally the notes in the update chapter.

Start menu with three clients
An administrator account is required to create a database (= client). The SQL Administrator usually has the user name"sa" and was entered without a password when the SQL Server was first installed.

After creating the client, the user "EULANDA" with password "eulanda" is created as the logon user. This is entered in the SQL Server role "EULANDA_Superuser" and has all rights to the EULANDA® database, except the possibility of endangering database consistency.
Note the license terms when creating new clients. In the basic version of EULANDA® only one client is allowed. Additional clients are only possible with extension licenses, the license is checked and a message is sent to our server in case of inadmissible clients!

If an administrator logs on to the EULANDA® system, he is made aware that the extended administrator rights could break the consistency rules and thus destroy the database. Therefore, only log on to the EULANDA® system as an administrator in exceptional situations.

Alias and client

The following description is intended for the administrator of your EULANDA® system.

In EULANDA® a client corresponds to a database of the SQL server. The access data to this database, i.e. the information such as the name of the SQL server or its IP number, the login user name and the login password, are stored in a UDL file.

UDL files are files managed by the operating system and contain all the information needed to access an SQL database.

EULANDA® uses two storage locations for UDL files. Normally the UDL files are in the folder of the EULANDA® main program. Accordingly, there is at least one UDL file for each client created.
udl file in the application directory
It is also possible to have several UDL files point to a database - this could be the case, for example, if you want to log on to the SQL server with different rights or use an alternative network library.

If clients are created in the EULANDA® start menu, the corresponding UDL file is automatically generated and stored in the program folder. If the user is not authorized to store files in this folder, the UDL file is stored in the user folder for applications. A user always has the necessary rights to this folder. This alternative location depends on the operating system used.

EULANDA® uses both locations to read the UDL files and display them in the start menu - the main folder of the program and the user folder for applications.

By changing the file name of the UDL file, you can influence its display sort. By default, the file names from both locations are sorted alphabetically. However, if you want a different sorting, you can force a different sorting by changing the number after the EULANDA® prefix.
Example 1:
Eulanda_5 EULANDA Software GmbH.udl
Eulanda_5 Anton Meier OHG.udl

The display in the start menu would be here:
Anton Meier OHG
EULANDA Software

Example 2:
Eulanda_1 EULANDA Software GmbH.udl
Eulanda_5 Anton Meier OHG.udl

The display in the start menu would be here:
EULANDA Software GmbH
Anton Meier OHG
The number between the EULANDA® prefix and the display name allows you to change the order as you like. If the digits are identical, the names within the digit group are displayed alphabetically again. Digits up to 9 digits are supported.

In the file name, the word "Eulanda" is followed by an underscore "_" and a space after the number.

UDL files can be distributed in the network, allowing the administrator to quickly update local EULANDA® installations with additional clients. For example, a UDL file can also be sent by e-mail to make it easier to connect branches, for example.

UDL file

Settings in the udl file

UDL files are managed by the operating system and can be modified using the property editor contained in the operating system - simply double-click the UDL file. The UDL file is normally stored in the EULANDA® program folder. The easiest way to access them is via the start menu under "Administration".

Edit udl file


The first file card sets the provider to the database system. This must not be changed and must be"Microsoft OLE DB Provider for SQL Server".

1. server name
Set the most important data on the connection tab. The first field contains the server name. This is already entered by EULANDA®, but it can be changed, for example to use an IP number instead of the PC name of the server. This would have the advantage that the computer name would not have to be resolved and, depending on the network configuration, no unnecessary router connection to the DNS server would be required.

If you use TCPIP (default) as network library, a port number to the SQL server is also accepted here, separated by commas. The default port is 1433, for a firewall, but also for router connections via NAT, it may be necessary to use a different port. Here, the SQL server must also be configured to the different port.
2. login information
In an NT server network, the logon can take place via the NT security system. This is easiest for users. However, a corresponding authorization must always be defined in the SQL server, otherwise normal domain users would have no rights to the SQL server. To set this, you need EULANDA® Client/Server and the full version of the SQL server that contains the Enterprise Manager. Alternatively, you can use the logon using SQL security. During the installation of EULANDA® the user "Eulanda" was predefined with the password "eulanda" and the most important authorizations. When the SQL server was installed, the SQL administrator or system administrator was defined with the user name"sa" and an empty password. This administrator should be given a password immediately.
Saving SQL passwords must be specified separately in the dialog box. If an empty password is saved, this must also be specified. Unlike NT security, SQL passwords are stored in plain text; you are made aware of this when saving. When it comes to security-relevant data, NT should be used in conjunction with NT security or no password should be stored and the password should be entered for each database login.
3. database
The database is preset when the client is created and should not be changed. It is the real database name, not the alias that is displayed in the EULANDA® start menu.
After changing the data, the database connection can be checked.

Entries in connection with EULANDA® are never to be made on this tab.

The database connection concept is based on OLE DB. All setting values are transferred to the database provider as ASCII text. Values that are not listed in the index cards can be checked and changed under "All".
The only value that could be changed would be the name of the network library. This should be set to TCPIP, i.e. named "dbnetlib". This is the DLL name of the transport driver. You can view the installed transport drivers via the program cliconfg.exe from the System32 folder of your system hard disk. This additional program can also be called from the start menu under "Administration".

Delete client

Deleting a client consists of logging off the database from the SQL server, deleting the files that become available as a result, and deleting the menu entry. A client should always be deleted from the start menu, since all these steps are followed.
Never delete a database file *.MDF or *.LDF in the file explorer; otherwise the SQL server can no longer start without errors. A database must always be removed by the SQL server itself!
In addition to deleting the database via the start menu, there may be special cases that you want to take into account manually. For this reason, further methods for deleting a database are described here.

Removing a Database Using the SQL Designer

After starting EULANDA® the SQL-Designer can be called via the right mouse menu under "Administration". In the SQL Designer, you can then select "Delete database" from the "Macros" menu. The macro can then be executed with Ctrl+E. To be on the safe side, compare the name of the database. This must match your client name, except that the client name is preceded by"Eulanda_".

Remove database via OSQL

Call an MSDOS prompt and change to the path "C:\Programme\Microsoft SQL Server\80\Tools\Binn". There you start the program OSQL.EXE with the following parameters:
In this example, we start from the standard case. Here the SQL administrator is the user"sa" and the password is empty. The letters -U and -P must be used in upper case, the user name and password must border directly on these letters.
If the information is correct, the SQL server responds with a prompt.
Now enter these two lines:
The name EULANDA_MyName must be replaced by the database name you are using. If you do not know exactly what it is, you can find your database in the folder "C:\Programme\Microsoft SQL Server\MSSQL\Data". The file extension is not part of the database name.
The program OSQL can be exited with the command "EXIT". Then delete the corresponding UDL file from the EULANDA® main directory.

Removing a Database Using the Enterprise Manager

Start the Enterprise Manager from your Start menu and select the"Delete" function above the name of your database using the right mouse menu. Then delete the corresponding UDL file from the EULANDA® main directory. The Enterprise Manager is not included in the scope of delivery of EULANDA®.

Delete menu entry for client

After removing the database, the menu item should also be deleted. By default, this is located in the EULANDA.EXE folder and always has the file extension".UDL". If the database is "EULANDA_MyName", the menu item is named "EULANDA_1 MyName.UDL". Remove this approx. 1KB large file in your file explorer.