Professional Documents
Culture Documents
WORKSTATION INSTALLATION
Note: Windows 8, Server 2012 is only supported from Version 4.6h onwards of VetlinkSQL. To check your
version go to the Help menu then about.
1. Create a new user profile if necessary. Make sure the name is less than 16 characters and
contains no special characters or spaces. Also the name must be unique to any other user
using VetlinkSQL.
2. Disable ‘User Account Control’ (UAC) from windows control panel if using Windows vista
or Windows 7.
4. Ensure the new user has full read and write privileges to the VL2 folder and sub directories
on the server, as well as the Registry and System 32 directory on the local machine. CFL
recommends the User to have Full Local Admin rights.
NOTE: Every time VetlinkSQL is loaded it will check the files in the local
‘Livedata’ folder are up to date. If they are not, VetlinkSQL will copy the
new files from the server to the local ‘Livedata’ folder. Also each user
has its own setup files which are saved on the server, so write privileges
are essential to update these files.
5. Run the Workstation installer from ‘...\ CFLAPPS \ VL2WSINS.exe’ (Contact CFL if the
installer is not here).This will create the shortcuts, create a local livedata folder and install
the Firebird ODBC driver. The livedata folder will usually be under ‘C:\VL2\Livedata’.
Target Set Up
Target Part 1 Full path to the VL2 executable, using the
"Shared Executable Directory", for example
M:\VL2\VL2.EXE
Target Part 2 Is the directory where the shared application
executables are found, for example M:\VL2\.
Target Part 3 Is the directory where the shared data is found,
for example M:\VL2\DATA.
Target Part 4 Is the directory where your local data will be
kept, for example C:\VL2\LIVEDATA. Each
user must have its own Local Data Directory.
Start In Is the directory that the application must
start in. This must be set to the "Local Data
Directory".
Additional Parameters
/noodbccheck Disables ODBC registry entry checking (use only if urgently
required).
/nowallpaper Disable wallpaper. Mainly used for Terminal Services
6. By default the new user will be assigned to the ‘Default’ config. The ‘Config’ file saves
printer and other set up options that are common to a group of workstations. To change the
‘Config’, or create a new one please refer to the ‘Config’ setup manual.
7. Test the ODBC drivers. See ‘ODBC’ setup manual for more details.
8. Install printer drivers and make sure the printers can print a test page in the correct size. If
you are using an existing ‘Config’ the printer drivers must have the same names as the
existing workstations.
9. If you have set up a new ‘Config’ set the printers in VetlinkSQL and ensure you have
initialised reports from ‘Picklist’ setup. Please refer to the ‘Printer’ setup manual for more
details.
10. Assign the Default Till and Store for this user from Options | Setup | Bill | User | Till
Number to Use / Store Number to Use. (Contact CFL if new Till and Store need to be set
up).
1. Create a new user profile if necessary. Make sure the name is less than 16 characters and
contains no special characters or spaces. Also the name must be unique to any other user
using VetlinkSQL.
2. Disable ‘User Account Control’ (UAC) from windows control panel if using Windows vista
or Windows 7.
4. Ensure the new user has full read and write privileges to the VL2 folder and sub directories
on the server, as well as the Registry and System 32 directory on the local machine. CFL
recommends the User to have Full Local Admin rights.
NOTE: Every time VetlinkSQL is loaded it will check the files in the local
‘Livedata’ folder are up to date. If they are not, VetlinkSQL will copy the
new files from the server to the local ‘Livedata’ folder. Also each user
has its own setup files which are saved on the server, so write privileges
are essential to update these files.
Target Set Up
Target Part 1 Full path to the VL2 executable, using the
"Shared Executable Directory", for example
M:\VL2\VL2.EXE
Target Part 2 Is the directory where the shared application
executables are found, for example M:\VL2\.
Target Part 3 Is the directory where the shared data is found,
for example M:\VL2\DATA.
Target Part 4 Is the directory where your local data will be
kept, for example M:\VL2\LIVEDATA1. Each
user must have its own Local Data Directory.
Start In Is the directory that the application must
start in. This must be set to the "Local Data
Directory".
Additional Parameters
/noodbccheck Disables Odbc registry entry checking (use only if urgently
required).
/nowallpaper Disable wallpaper. Mainly used for Terminal Services
6. By default the new user will be assigned to the ‘Default’ config. The ‘Config’ file saves
printer and other set up options that are common to a group of workstations. To change the
‘Config’, or create a new one please refer to the ‘Config’ setup manual.
7. Test the ODBC drivers. See ‘ODBC’ setup manual for more details.
8. Install printer drivers and make sure the printers can print a test page in the correct size. If
you are using an existing ‘Config’ the printer drivers must have the same names as the
existing workstations.
9. If you have set up a new ‘Config’ set the printers in VetlinkSQL and ensure you have
initialised reports from ‘Picklist’ setup. Please refer to the ‘Printer’ setup manual for more
details.
10. Assign the Default Till and Store for this user from Options | Setup | Bill | User | Till
Number to Use / Store Number to Use. (Contact CFL if new Till and Store need to be set
up).
CONFIG FILES
OVERVIEW
Each user in VetlinkSQL is assigned to a configuration group. The configuration group a user is assigned to will
determine which printers are used, which report templates are used and some setup options. By default the
user will be assigned to the default config. The user will be created automatically from the Windows
username.
To check which config a user is assigned to look at the top of VetlinkSQL in the Title bar. In the example below
‘kieran’ is the ‘User’, ‘Default’ is the ‘Config’. Any other user that is sharing the ‘Default’ config
will have the same printer settings.
Config’s are generally determined by location and which printers a user needs to print to. For example, in
the office upstairs they may have their own printers. Users upstairs can be assigned to the ‘Upstairs’ config.
Users downstairs could be assigned to the ‘Downstairs’ config as they have their own printers.
IMPORTANT: You may also need separate configs if printers are connected to machines locally rather than IP
printers. As printers are saved by their driver name in VetlinkSQL their driver name can be different on two
computers, even though they are printing to the same printer. For example, on the ‘User1’, where the
printer is connected, the printer name is ‘HP Laserjet’. On ‘User2’ the printer will be ‘HP Laserjet on User1’.
In this scenario two configs would be required. Therefore CFL recommends IP printers.
3. Check if the ‘*.cfg’ file you want exists. If not copy ‘Default.cfg’, or a config you know will
have similar settings, and rename it. The config name must be less than 5 characters.
4. Look for ‘*.usr’ file you want to change and open it in notepad.
6. Open VetlinkSQL and check the ‘Title bar’ has loaded the correct config.
If you have created a NEW config. In VetlinkSQL go to Options | Picklist Setup | Reports | Special Reports |
click ‘Yes’ to message asking to initialise defaults for reports.
ODBC DRIVERS
SETTING UP ODBC DRIVERS
1. Run the firebird ODBC driver installer from ‘\ CFLAPPS \ Firebird \ Firebird_ODBC_2.0.0-
Win32.exe’.
5. Setup the ODBC driver with the following options. Options not specified below can be left
blank.
6. Click on ‘Test Connection’. If set correctly you should see a message saying ‘Connection
Successful!’. If you do not receive a successful connection review options or contact the
VetlinkSQL help desk.
2. Go to ‘C:\Windows\SYSWOW64\odbcad32.exe’.
5. Setup the ODBC driver with the following options. Options not specified below can be left
blank.
6. Click on ‘Test Connection’. If set correctly you should see a message saying ‘Connection
Successful!’. If you do not receive a successful connection review options or contact the
VetlinkSQL help desk.
PRINTERS
SETTING UP PRINTERS IN WINDOWS
Before printers can be configured in VetlinkSQL the printer drivers must be set up in windows on the
workstation. When setting up printers CFL recommends printers are set up as IP printers rather than
attached to a local machine and shared.
If your printer has two trays and you are printing both A5 and A4 paper CFL highly recommends setting up
two print queues. One to print only to A4 paper and one to print only to A5 paper.
PRINTER
PRINTING
GROUP
REPORT
assigned to a
TEMPLATES PRINTER
CONFIG assigned to a
PRINTING GROUP
contains
REPORT
USER TEMPLATES
assigned to
a CONFIG
3. Click on the ‘Printer’ button and select the ‘1: Printers’ tab.
5. On the right hand side under ‘Windows Name’ select the printer you wish to use for that
group. Only printers installed in windows will be shown.
6. Once you have selected the printer click on the ‘Accept’ button to save.
3. Select ‘Reports’.
4. Depending on the report you want to find double click on ‘Special Reports’ or ‘Other
Reports’. See Report Template Locations section.
Reciepts / Invoices
Tax Invoice Other Invoice SR-001 Tax Invoice
Tax Receipt Other Invoice SR-002 Tax Reciept
Diary Forms
Surgery Consent Special Diary SR-088 Diary Consent
Address Confirmation Special Diary SR-089 Diary Address
New Client Special Diary SR-090 Diary_New_Cln
Desexing Consent Special Diary SR-177 Desexing Consent
Euthanasia Consent Special Diary SR-178 Euthanasia Consent
Custom Consent Special Diary SR-179 Custom Consent
End of Day
EOD Banking Special EOP SR-014 EOD Banking
EOD Till Rolls Special EOP SR-015 Till_Roll
EOD Payment Slip Special EOP SR-016 Payment Slip
EOD Sales Summary Special EOP SR-017 EOD Sales Summary
EOD In House Special EOP SR-025 Daily_InHseRpt
EOD Breakages Special EOP SR-126 Daily_BrkgeRpt
End of Week
EOD Sales Summary Special EOP SR-018 EOW Sales Summary
EOW Staff Perf Special EOP SR-022 Weekly_StaffRpt
EOD In House Special EOP SR-026 Weekly InHseRpt
EOD Breakages Special EOP SR-127 Weekly_BrkgeRpt
Clinical History
Clinical History Last Other Animal SR-102 Animal History_Last
Clinical History Last 3 Other Animal SR-113 Animal_Last3_Hist
Clinical History All Other Animal SR-114 Animal_All_Hst
Clinical History Other Animal SR-134 Animal_History
Medical Insurance Other Animal SR-137 Anm_Med_Insurance
Clinical History Current Other Animal SR-225 Animal_History_Current
Labels
Product BC Labels Other Products SR-040 Prd_BarCode
Shelf Talker Other Products SR-192 Shelf Talker Label
Other
Product Handouts Doc Product SR-226 Product Handouts
Vouchers Other Invoice SR-164 Vouchers
Label Sizes
BARCODE SCANNERS
RECOMMENDED BARCODE SCANNERS
Symbol LS2208
All of these recommended barcode scanners can be purchased from CFL pre-programmed for use with
VetlinkSQL.
CONFIGURING VETLINKSQL
1. Go to ‘Options’ and then ‘Setup’.
2. Click on the ‘Misc’ button and then the ‘2: Bar Coding’ tab and make sure ‘Using Barcode
Scanner’ is ticked.
3. If you have a complex barcode scanner make sure ‘Complex Barcode Scanner’ is ticked
(most scanners are usually simple).
In order for the software to determine whether the method of entry of these numbers is by barcode scanner
or keyboard, it is necessary for the barcode scanner to send identifiers in the string of numbers it returns. If
the program is able to distinguish between an entry made by a barcode scanner and a keyboard, it is able to
block “accidental” scans from a barcode scanner going to the wrong section of the program. For this reason
the barcode scanners need to be specifically programmed with correct preamble / prefix and an inter-
character delay.
CFL has barcode programming sheets already prepared for the recommended scanners. Scan through each
of the barcodes in order to program your scanner. Other barcode scanners may also work with VetlinkSQL but
will need to be programmed with the correct preamble / prefix. If you wish CFL to program a non-
recommended barcode scanner it will be charged at our standard hourly rate.
To test the scanner open notepad and scan a barcode label. The barcode must begin with the pipe symbol,
‘|’, and then the barcode number.
Simple BC Sheet 1
Simple BC Sheet 2
Simple BC Sheet 3
Simple BC Sheet 4
Simple BC Sheet 5
Simple BC Sheet 6
Simple BC Sheet 7
Simple BC Sheet 8
In order for VetlinkSQL and HairlinkSQL software to work on your machine your barcode scanner must be set up
to:
1. Send a prefix (the pipe symbol, hex value 7C) with every barcode.
Follow the steps listed below for non-CFL supplied barcode scanner setup. Some of the steps may not apply
to your particular scanner, refer to your instruction manual for more details.
1. Disconnect the power to your computer before plugging in/unplugging any cables to avoid
any possibility of damaging your hardware. Plug in your scanner.
2. We recommend that you reset your barcode scanner to “factory settings” or “factory default”.
Find the “return to factory settings” instructions for your barcode scanner in your barcode
scanner “programming guide” or “instruction manual” and follow them through to completion.
3. (Most scanners require this step). Specify the keyboard wedge settings for your scanner.
VetlinkSQL and HairlinkSQL users will usually have either PS/2 or AT keyboard interfaces and
the setting for both these interfaces will usually be represented by one interface type (they
are, as far as the barcode scanner is concerned, the same).
4. (Some scanners don't require this step). Specify that the barcode scanner is attached to a
keyboard. Some scanners need to know whether a keyboard is attached to know whether to
send an acknowledge signal to the PC, or whether the keyboard will provide this signal.
5. Reading your instruction manual, you must now determine how the scanner handles the
sending of prefixes and barcode label identifiers. There are a number of different ways in
which a scanner can manage the sending of these control codes. I will cover the two most
common methods a barcode scanner uses.
Method 1: The preamble or prefix codes are set separately to the label identifiers. ie. You set the
preamble/prefix only once, then you set the identifier for each different type of barcode label
separately, without re specifying the preamble each time.
Method 2: The preamble or prefix codes are set with the label identifiers. ie. You set the
preamble/prefix every time you set a label identifier.
6. (Method 1 only) - Reading your instruction manual, you must now determine how to send a
preamble/prefix with the barcode number. You must set this preamble/prefix to be the pipe
symbol (|) Hex value “7C”.
For example, you might scan the “Start of Configuration” barcode in your instruction manual,
then the “Preamble=?” barcode, followed by the barcode for “7” and “C”. This says “Every
time I scan a barcode, regardless of its type, I want to send a pipe symbol first”. Depending
on your scanner, you may at this point scan “End Configuration”/ “Save Configuration” or you
may have to continue with Step Seven before ending this session and scan an interim “Set”
barcode to continue with the next instruction.
(Method 2 only): - Reading your instruction manual, you must now determine how to send a
prefix and label identifier with the barcode number. You must set this barcode prefix and
label identifier to be the pipe symbol (|) Hex value “7C” AND the first label identifier hex
code. Repeat this process for each of the five label identifiers. See the list below for the label
identifier codes that you have to enter.
For example, you might scan the “Start of Configuration” barcode in your instruction manual,
then the “UPCA=?” barcode, followed by the barcodes in your instruction manual for “4” and
“1”. This says “Every time I scan a UPCA barcode, send an “A”, followed by the barcode”.
Depending on your scanner, you may at this point scan “End Configuration”/ “Save
Configuration” or you may have to continue with scanning an interim “Set” barcode to
continue with the next instruction.
7. (Some scanners don't require this step). Set the inter-character delay to 5ms. For example.
Scan “Start of Configuration”, “Set”, “Intercharacter Delay=5ms”, “Save”
.
8. To confirm that you have programmed the scanner correctly, open a command prompt and
scan a product barcode. You should see the following character in front (prefix) of the actual
barcode number. eg. |F9780582878426.
CASH DRAWERS
SETTING UP CASH DRAWERS
Any cash drawer with a serial cash drawer solenoids kicker can be used with VetlinkSQL. Once you have
connected the solenoids kicker to a serial port on the PC, use ‘VL2SETUP’ to select the correct serial port and
baud rate for your drawer.
3. Set Type of Draw to the Com Port it is attached to. If you only have s USB port, then a USB
– Serial converter will be required.
EFTPOS SETUP
SETTING UP EFTPOS INTEGRATION
Supported Terminals (NZ ONLY)
Hardware Connection
A serial or COM port is used to connect the EFTPOS terminal to a computer running HairlinkSQL or VetlinkSQL.
The serial cable will be supplied by the EFTPOS vendor and the Eftpos terminal cannot be shared between
computers.
Configuring Vetlink
3. On the machine connected to the Eftpos machine go to ‘Options’ and then ‘Setup’.
5. Set the driver to the type to the type of Eftpos terminal you have.
IMAGING DEVICES
Flatbed scanners, digital cameras and web cameras can all be used to attach images to client, animal and
clinical records within VetlinkSQL. In order to select the type of imaging device that you will be using go to
Options | Setup | Miscellaneous | General.
FLATBED SCANNERS
1. Install the Windows flatbed scanner driver.
2. Under the Type of Camera drop down menu select Twain Compliant.
3. Under the Twain Scanner select the scanner you have installed
DIGITAL CAMERAS
1. Install the Windows digital camera driver.
2. Under the Type of Camera drop down menu select Mass Storage device.
3. Under the Camera Folder select the folder on the camera‟s memory card where the images
are stored.
WEB CAMERAS
1. Install the Windows web camera driver.
2. Under the Type of Camera drop down menu select Twain Compliant.
3. Under the Twain Scanner select the web camera you have installed
LAB MAIL
WHAT IS LABMAIL?
Labmail is a specifically crafted email. The emails are designed to be recognised by veterinary software
packages and processed according to the governing rules. Labmail allows your Veterinary Diagnostics Lab to
send an email containing written analysis of the diagnostics you have requested directly back in to VetlinkSQL.
SUPPORTED LABORATORIES
Gribbles NZ, Gribbles Aus, Laverty, NZ Pathology, Idexx, ASAP
7. Close the ‘Animal Setup’ window first and then select ‘File’ and ‘Exit’ from the drop down
menu in the top left corner. You will be presented with the ‘Confirm’ (Save Changes)
window. Click the ‘Yes’ button.
8. Now that Labmail is active within VetlinkSQL all that is left to do is configure your mail
server, poplink (application developed by VetlinkSQL) or the laboratories lab email utility
(eg. eclinic for gribbles) to place all labmail destined for VetlinkSQL into the
‘\VL2\DATA\LABMAIL\NEW’ folder.
NOTE: If you would like to purchase poplink please contact sales@cfl.co.nz for a quote.
2. Select the ‘New’ button at the bottom right and you should see the layout below.
3. Enter the ‘First and Last name’, ‘Email Address’ and any other information required.
4. Select the ‘Mail & Attachments’ tab in the ‘Account Settings’ panel. In the ‘Mail Folder
type in ‘?:\VL2\DATA\LABMAIL\NEW’. This is the location of your VetlinkSQL install.
5. Select ’OK’ and that will be all that is required for most Mdaemon operators.
6. If you are not using a fully qualified domain name for your mail then you may have to setup
an address alias. This consists of typing in the email address that the labmail is being sent to
and associating it with the internal address that Mdaemon is using. Please see the example on
the following page for reference.
If you have followed all these steps and you labmail does not appear to be working please contact CFL on (09)
4892280.
4. Select the ‘Export HTML files to folder’ and make sure it points to
‘...VL2\DATA\LABMAIL\NEW’ folder.
PDA CONFIGURATION
SOCKET SCAN
Scanner Settings
The SocketScan configuration utility lets you specify prefix and/or suffix characters to be added
automatically to the data you scan, as well as sounds to indicate a good read.
1. Tap on the ‘SDSC’ scanner icon, , at the bottom of the Today screen.
2. The ‘Scan Wedge’ icon will pop up in the PDA tray on right bottom corner
OPTICON PDA
1. Tap the barcode icon at the top of the screen.
2. Tap on ‘Settings’.
The Pocket PC's internal RAM is not permanent memory, unlike data stored on a floppy or hard drive.
Continuous power is required to retain the data. Therefore follow these simple steps to protect yourself
from data and program loss.
1. After creating a partnership with ActiveSync, make sure you back up your Pocket PC on a regular
basis. This is a must do! Otherwise you will lose your programs and data if your battery dies, or if you
have a serious crash and are forced to hard-reset your Pocket PC.
2. Use the soft reset feature of your Pocket PC on a regular basis. This will clear your memory of
unwanted files and programs still running in the background. This minimizes crashes and also can
help you recover from a mild crash.
3. Always keep your battery level above 30%, and recharge your batteries every chance you get. Newer
lithium-ion will last longer and retain a better charge when recharged regularly.
4. Make sure you have the latest version of ActiveSync installed on your desktop PC. You can download
it for free from Microsoft (http://www.microsoft.com/win...).
5. Always take your AC power adapter with you on day trips. Purchase a car charger as a backup if
possible. Once you lose power, you will lose your data and programs until you are able to do a
backup/restore.
“Protect from data and program loss. Use ActiveSync to back up your Pocket PC. Access this feature from the
Tools menu”.
(Bob Katayama, PocketPCMag.com Forum Moderator)
2. Open Microsoft ActiveSync on your PC, ensure ActiveSync has recognised the PDA and synchronised
files.
4. On the Backup/Restore screen, if you are backing up for the first time you must select ‘Full Backup’,
otherwise select ‘Incremental Backup’.
Fig. 24 - 30
5. Click the ‘Change’ button to select the destination for the backup file (this should be the same every
time you backup).
6. Click the ‘Back Up Now’ button to start the backup, this may take a few minutes depending on the
size of the data.
7. When the backup is complete; a message will appear stating ‘Backup operation completed
successfully’. You may now close ActiveSync.
2. Open Microsoft ActiveSync on your PC, ensure ActiveSync has recognised the PDA and synchronised
files.
4. On the Backup/Restore screen, in the ‘Backup’ tab, ensure the correct backup file has been selected,
use the ‘Change’ button to change the file if required.
Fig. 24 - 31
6. Click on the ‘Restore Now’ button to start restoring data from the backed up file.
The STOCKLINKSQL program and data files are stored on an SD card. SD memory cards are highly reliable
permanent storage media. Therefore files stored on SD cards are not prone to being lost when battery
power is lost.
However, SD cards come in different models and versions. We recommend that a high speed SD card is used
to achieve optimal performance. Please contact your STOCKLINKSQL supplier for recommendations on brands
and models.
Other Windows related files are also necessary, these are stored in the PDA’s internal RAM, this is not
permanent memory and therefore such files are prone to being lost when battery power is lost. However, in
cases where power is lost to the unit the data and program files are left intact as they are stored separately
on the SD card.
In this section we will describe installation and recovery procedures under different circumstances.
5. On the PDA, execute the cab files in the order they are listed above. If prompted to ‘over write files’
or ‘re-install’ files click ‘OK’ to continue.
6. Installation is now complete, STOCKLINKSQL is ready to use provided the appropriate registration
details have been entered into VETLINKSQL.
STOCKLINKSQL Recovery
The recovery process will replace Windows system files, the STOCKLINKSQL program files and database engine
files. If an Order or Stock Take is in progress the relevant files will not be affected. Any orders or stock take in
progress can be continued after the program recovery is complete.
5. On the PDA, execute the cab files in the order they are listed above. If prompted to “over write files”
or “re-install” files click “OK” to continue.
6. STOCKLINKSQL is now ready to use. This process does not over write data files created for Orders and
Stock Take.
A PDA cannot be used on a terminal services session. The problem is to do with Microsoft not supporting
redirection of USB ports in a Remote Desktop or a Terminal Services session. Re-direction of USB ports is
required so Active Sync on the TS session can detect that a PDA is connected on the local computer.
However, for clinics that are run over terminal services VETLINKSQL has provided a solution to make use of
your PDA for ordering a stock taking.
You must have local machine / fat client with a network connection and mapped drive to the VL2
database server.
The local machine must be installed with Microsoft ActiveSync version 3.8 or later. This is
synchronisation software for Windows Mobile powered Pocket PCs. You may download this from;
http://www.microsoft.com/windowsmobile/downloads/activesync38.mspx.
Each Terminal Services session must be set up with its own Livedata folder (a VetlinkSQL user based folder
specified in the VL2 shortcut).
‘VL2PDAInst.exe’ must be executed on the local machine. This will create an icon on the desktop to
import and export files to and from the PDA.
To install the VL2PDA application run the ‘VL2PDAInst.exe’ file. Just specify the location of the folder on
the Server where VETLINKSQL is located (by default M:\VL2) and click ‘Next’. The VL2PDA shortcut will be
created on the user’s desktop.
The ‘VL2IdexxInst’ installer must be run on the client machine where VetlinkSQL IDEXX background will be
installed.
1. Upgrade to VetlinkSQL version 4.2 or higher and enable the Idexx module on the VetlinkSQL
registration form.
2. Ensure the workstation running the VetlinkSQL IDEXX background is connected to the IDEXX Vetlab
station using a serial port cable. Check with Idexx if they can supply this otherwise, organize with
your hardware technician. A serial to USB converter can be used as well.
3. If the Idexx background is being run on a terminal services session make sure the serial port is being
passed through under local resources from RDP connection.
4. Disable User Account Control (UAC) on machine where idexx background is to be installed if IDEXX
client is installed in Windows Vista or Windows 7.
For Example: For Windows 7 go to; Start | Control Panel | User Accounts |
User Accounts | Change User Account Control Settings | Never Notify
and the restart computer / session.
5. Run the ‘VL2IdexxInst’ installer. Available at CFL under \\source\d\vl2idexx. Remember to install to
the network drive (usually M) and ensure the shortcut is set up correctly especially if the site has
multiple idexx backgrounds. Shortcut specifications are on the following page.
6. Enable the ‘GENLABB.L’ form in VetlinkSQL. Go to Options | Picklist Setup | History | History Forms |
+ | OK | select the GENLABB.L form from the list | OK. The ‘GENLABB.L’ template file should be
available under the folder ‘…\VL2\FORMS’ folder after updating to version 4.2.
7. If VetlinkSQL is not installed on the workstation as well you will need to make sure GDS32.dll is copied
from ‘C:\windows\system32’ on server to ‘C:\windows\system32’ on workstation.
Hardware Setup
The Idexx Lab station is connected to a User on the VetlinkSQL network by Serial cable. An application (Idexx
Background) is installed on a user profile which checks the serial port for results and then imports them into
the database.
The machine in which VetlinkSQL IDEXX background is running has to be connected to the IDEXX Vetlab
station using a serial port cable. Defaults should be entered from the VetlinkSQL Idexx installer .The shortcut
command line is set up as follows.
For Example:
Following values should be configured in the Idexx background before using the client application. ‘Setup’
menu option in the main screen is used to set the values.
Default values
1. Port number will be 1.
2. Number of bits will be 8.
3. Number of stop bits will be 1.
4. Parity will be ‘N’ means false.
5. Port speed (in bps) will be 9600.
6. Read interval will be 5 seconds. (client will read lab results every ‘n’ seconds)
7. Use TCP/IP option will be unchecked and the value will be blank.
There are two settings requiring activation on the IVLS PC to facilitate transmission of results to VetlinkSQL. It
is IDEXX’s responsibility to ensure that STEP 1 is completed.
STEP 1 (IDEXX)
S TE P 2
1. Make sure the VetlinkSQL Idexx Background is running and a serial cable is connected
between the IVLS PC and VetlinkSQL PC. If connection is successful a yellow PIMS icon will
appear at the bottom of the main menu on the IVLS PC.
2. Click on the yellow PIMS Icon
3. On the ‘Practice Management’ tab make sure that ‘On (records will be transmitted)’ is
selected. Please Note: The ‘Practice Management’ tab is only available if there is
communication between the IVLS and VetlinkSQL.
4. Ensure that the ‘Do not transmit records created before’ date is set to today‟s date.
Note: Should communication between the IVLS and VetlinkSQL be lost for any reason the green PIMS Icon will
turn Grey and display a disconnect icon. The practice management settings tab as indicated in STEP 2 above
can be accessed by clicking the greyed out icon.
BACKUPS
INSTALLING VETLINKSQL CD/DVD BACKUP
SCRIPT
IMPORTANT: Please make sure that you have Ahead Nero 5.5.7.8
or later installed on your system before beginning VL2 Backup
Script installation process!!!
1. Install 7-Zip version 3.13 or later by running 7-Zip Installer from 7-Zip folder.
4. Copy VL2Backup.bat (for CD backup) or VL2DVDBackup.bat (for DVD backup) and IBBACK.bat files
to the root of CFLAPPS folder (usually on D: drive)
5. Change drive letter of CD-RW drive inside VL2 backup script according to your system by:
a. Right click on . VL2Backup.bat (for CD backup) or VL2DVDBackup.bat (for DVD backup) and
click Edit
b. Change the –drivename parameter in Nerocmd command from “e” to the letter of your CD-
RW drive
c. Save changes by selecting File – Save
d. Select File – Exit to close Notepad
7. To run VetlinkSQL Backup put a blank CD-RW or DVD+RW disc into CD/DVD drive and double click on
VL2 Backup icon on your Desktop.
EMAIL SETUP
Before starting you will need to ensure that internet access is available from the computer that the
background is installed on. You must also have access to an outgoing mail server such as Xtra, Vodafone,
Bigpond or your own internal email server (Webmail accounts such as Google mail cannot be used). When
signing up for the internet an email account is usually included in the package.
Setting up email for the application works in a similar way to other desktop e-mail clients (e.g. Apple Mail,
Microsoft Outlook). You will need the host, port, username and password for your email account. If you are
unsure about the details you will need to call your email internet provider or Hardware Technician to obtain
the information.
Go to Options | Setup | Log in with username and password | Misc | Internet | Outbound Mail
Settings and enter the details in the appropriate fields.
Once all the information has been entered you must restart the Background processor before the changes
take effect.
New Zealand
Telecom Xtra smtp.xtra.co.nz or send.xtra.co.nz
Clear Net smtp.clear.net.nz
Paradise Net smtp.paradise.net.nz
Vodafone smtp.vodafone.co.nz
IHUG smtp.ihug.co.nz
Orcon mail.orcon.net.nz
Slingshot smtp.slingshot.co.nz
TROUBLE SHOOTING
ERROR 599
This is usually an ODBC error. Check your ODBC settings
ERROR 534
This is usually and ODBC error. Check you have ticked quoted identifier in the ODBC settings.
The Haematology Analysers that export PDF only are currently not supported. These files can be attached
manually, one at a time, using the PDF attachment function in the clinical history screen.
11. Make sure the ’Use Lab Email Module’ box is ticked.
13. Click on the ‘Animal’ button and select the ‘History’ tab.
15. Close the ‘Animal Setup’ window first and then select ‘File’ and ‘Exit’ from the drop down
menu in the top left corner. You will be presented with the ‘Confirm’ (Save Changes)
window. Click the ‘Yes’ button.
16. Now that Labmail is active within VetlinkSQL all that is left to do is configure your mail
server, poplink (application developed by VetlinkSQL) or the laboratories lab email utility
(eg. eclinic for gribbles) to place all labmail destined for VetlinkSQL into the
‘\VL2\DATA\LABMAIL\NEW’ folder.