ddrummey

Hi all I am hoping somebody out there may be able to help me with this one. I am trying to determine the best way of protecting an application we have built using LabVIEW7. The application: The application is an ATE system with the equipment control software written using LabVIEW7 and the tests sequenced using Teststand2. The application was built around TestStands operator interface for LabVIEW using LabVIEWs application builder. The required .seq files and a library of required LabVIEW functions (save using LabVIEWs

Hi Chris Thanks for your response, you mentioned that personally you would prefer to run without a dongle if you could avoid it. Have you experiance with any other protection methods that don't use dongles? An anti paricy package called "CrypKey Instant" seems to have been used by labVIEW users before (I noticed it mentioned in a tread on NIs disscusion forum). Anyone have experiance with this? Any further advice would be much appreciated. T.I.A Declan

Just thought of someting else. Did you build an installer? under the advanced tab in the installer option there is a check box to include runtime engine support for report generation. Did you check this box?

Hi Mike I have attached a word Doc containing a few bits of info is saved recently when experiencing a similar problem, you may be aware of them but thought they might be of interest to you. Download File:post-1501-1107253266.doc

Hi Jack, Chris and Mynoch I know this tread is quite old but was hoping you might still check . I found the tread of real interest to me as I was concidering percasing the super pro key to protect my labVIEW program. I am running with LabView 7 at the mo. From the obvious interface problems mentioned here is it worth my while getting this software or have you any other sujestions of a more suitable alternative. Mynoch, how did you eventually get on with the keys. did you get the software to work for you. Any advice would be much appreciated. Kind Regards Dec