Hi Bob (Not Robert Pavlis, President of Labtronics, I hope

),
We have two versions of LIMSLink. The first is between Agilent ChemStation Plus (v. A.09.01/B.02.01) and Applied Biosystems SQL*LIMS. THis was installed in March 2003 and was used till the end of last year when we migrated to Agilent Cerity. We now have an interface between Cerity (A.02.01SR2) and AB SQL*LIMS v 4.0. Other sites within the company have installed LIMSLink between Waters Millennium and AB SQL*LIMS.
With the latest version (LIMSLink-CDS 3.2), we did an evaluation against several other vendors. The only one that came close to having a product with functionality that met out requirements was the CSols product. We eventually went with Labtronics because of previous experience with the product and because the latest version would integrate into Cerity.
The previous version (ChemStation-SQL*LIMS) was heavily custom coded and didn't use much of the default functionality in LIMSLink. However, that showed the power of the product, because so long as you have someone that can code in Visual Basic, you can custom code LIMSLink as much or as little as you want.
The current version we are using has been used off-the-shelf, with no custom coding at all. It integrates well with Cerity and even better with Millennium (using the toolkit). Biggest limitation that has been fedback from the labs is the number of batches they can get into one sequence (6-7). That is partly because of the way we configured the SQL queries in LIMSLink - if we'd written the SQL queries in a different way, we could probably get more.
The result-return side of the product is good too. The custom coded version has a direct database link into the ChemStore database. The version for Cerity uses flat-files. That was the hardest part of the process - getting reports in a format that LIMSLink could split and parse that data out of. Actually configuring LIMSLink to split and parse the reports was quite easy.
One of the other benefits that convinced us to use LIMSLink was that it can be used to interface with other Lab equipment - balances, UVs, KF, etc. That is a future project, but the functionality is there out of the box.
Final benefit, though we don't use it, is the Special Functions toolkit that is available for LIMSLink. Adds on additional functionality (including the Visual Basic scripting engine) that mean LIMSLink can perform additional processing on the data before it gets sent to LIMS. That means you can eliminate Excel spreadsheets - data automatically goes into LIMSLink, gets processed and automatically sent out to LIMS.
We estimated that the interface saved us an average 100,000 manual data entries per year over the past two years.
Final point was with Labtronics themselves. They are a good crowd to work with and the application experts really know the product well. On occasion we felt they over-estimated what LIMSLink was capable of, especially with the Cerity version, but eventually worked round the problems.
That's probably more information than you asked for, but if you need any other info, please ask!
Tim