ClientIniPath Property

Syntax

Object.ClientIniPath = path
Type = string, read/write

Description

The ClientIniPath property allows the use of an “LLMWClnt.ini” file for the control to read the properties from the LPS.  Upon setting this property, the file is parsed and an internal mapping of all servers and corresponding printers takes place.  The llmwclnt.ini file needs to be created in a directory somewhere on your network.  The “LabelsPath”, “LayoutPath”, “PrinterPath”, “DropDirectory” as well as “ServerName” and “ServerAlias” properties for multiple servers are specified in the .ini file.  If you are only using one Lofware Server (LPS), you need not use this property, and the other properties listed above can be set in code.  The following syntax example shows an .ini file listing two LPS servers.  Setting the "ClientIniPath" property to point to this file causes the control to be set up for multiple LPS servers.  The ServerCount property is actually equal to 3 after setting the ClientIniPath to this .ini file.  Server 0 is the default server that existed before the setting of ClientIniPath. Server 1 and 2 correspond to the ones listed in the .ini file.

The LLMWClnt.ini file can also be used to connect to multiple servers through socket connections.  When  used in this way, it is not necessary to specify the “Labels Path”, “Layout Path”, “Printer Path”, “Drop Directory” or “ServerAlias” properties in the .ini file, only the “Server Name” and the “IPAddress” property are required.  Any application using the ActiveX Control automatically logs in to all the servers listed in the LLMWClnt.ini upon execution of the program.  Once you are connected to multiple servers, you can use the “SetServer” Method to move between servers.

Note: This property is what allows the Client Control to be aware of multiple Loftware Print Server Installations. See the section called “Performance Considerations” in Chapter 1 for information to help you to decide when you need to divide your printing load among multiple servers.  Chapter 1 also has more information on the syntax requirements of the llmwclnt.ini file.

Syntax of llmwclnt.ini file:

[Receiving1]
Name=JANAA
Alias=Jana Computer
LabelsPath=c:\program files\Loftware Labeling\labels
LayoutPath=c:\program files\Loftware Labeling\Layouts
PrinterPath=c:\program files\Loftware Labeling
ScanPath=c:\program files\Loftware Labeling\wddrop
[DemoRoom]
Name=TRAINING
Alias=Training Room Server
LabelsPath=\\training\Loftware Labeling\labels
LayoutPath=\\training\Loftware Labeling\layouts
PrinterPath=\\training\Loftware Labeling
ScanPath=\\training\Loftware Labeling\wddrop

Example

'get a list of LPS servers and populate a list box with their names and
'aliases. This List could later be used to decide which server to set with the
'SetServer Method.

On Error GoTo Handler
frmFront.ClientX1.ClientIniPath = Trim(txtClientIniLocation.Text)
For i = 1 To frmFront.ClientX1.ServerCount - 1
  frmFront.ClientX1.SetServer (i)
  lstServers.AddItem frmFront.ClientX1.ServerName & " ALIAS " & frmFront.ClientX1.ServerAlias
Next I

Syntax of llmwclnt.ini file using Socket Connections

[Shipping1]
Name=SHIPLINE1
Address=165.10.0.120
[Receiving1]
Name=RECEIVING1
Address=165.10.0.122

See also:

ServerCount

ServerAlias

ServerNumber

PrinterPath

ServerName

SetServer