|<WatchDirectory> || - ||The directory FileWatcher is watching |
|Queue || - ||Tells FileWatcher to transfer the file to a Windows Print Queue |
|<Printer Name> || - ||The Windows Printer name OR the code in the windows translation file |
|<FileName> || - ||Any unique filename |
|.fw || - ||The required suffix. Only files with this suffix are processed |
The Queue Translation File
The Queue Translation file is just a text file with a series of lines with one translation per line. Each translation is of the form:
<Translation Name>=<Printer Name>
<Translation Name> - The information FileWatcher will find in the file name<Printer Name> - The Windows Printer name to send the file to
For example, if the <Translation Name> on the file is "Handheld" and the printer name to send the file to is "Label1", the following line would be in the translation file:
FileWatcher will only look for updates to the configuration file at startup time. Please restart the service if changes are otherwise desired.
The FileWatcherService.exe.config is the first configuration file used to point to the proper file changes.
- The "Watch" directory
- The "Queues.txt" location
- The "Save" path
Using FileWatcher from a Label Control File
Configuring a label control file to use FileWatcher requires two steps.
- Remove any lines starting with [QUEUE]
- Add or modify the line starting with [FILE] to output the label to the filewatcher directory using the proper filename syntax.
Using FileWatcher to Generate a Crystal Report
A Crystal Report may be generated by using FileWatcher anywhere in the Handheld WMS or Shipping solution calls to the labeling system.
As stated in the above "Format Filename" section of this tutorial, the typical FileWatcher format for sending a file to a printer is:
However, if it is desired to generate a Crystal Report, the FileWatcher format is:
The contents of this file is in XML format, as follows:
<Parameter Name="Pallet ID" Value="P123" />
|Database || = || Specify the SQL database to use |
|Report || = || File name of crystal report |
|Parameter || = || Parameter to be sent to the report (multiple parameters are allowed) |
|SavePDF || = || Save a copy of the report as a PDF (Default = No) |
|Copies || = || Number of copies to print (Default = 1) |
|Name || = || Name of parameter in the report |
|Value || = || Value to which the parameter will be set |
The new registry entries for the Crystal configuration to set access to the SQL server:
|ReportPath || = ||Path to where the Crystal report files are stored on the server |
|OutputPath || = ||Path to where the PDF copies should be stored (if requested) |
|SQLServer || = ||Specify the SQL server to use |
|SQLUser || = ||SQL Username (must be SQL username, not windows authentication) |
|SQLPassword || = ||SQL Password for Username (will be encrypted when Filewatcher is next restarted) |
- the Crystal report is completely responsible for all database access.
- in the report, all database connections must be done use OLE DB (not ODBC, or any other method). If the report is being created on a different machine from the server, the same provider that is available on the server should be selected during the OLE DB setup.
- Remember the SQL Username and Password must be a SQL user-- Windows integrated security is not supported.
- The printer name will go through the same translation that it does for the standard "Queue" option.
- If the report fails to print, check the Windows Application event log for errors.