USB-6008 How to move an executable to a different computer.

[Dennis_Knutson]

There are no drivers included with the runtime engine. There is no evaluation period for MAX or license for it. There are no projects associated with MAX. I really don't know what you are doing.

[JÞB]

---

@Dennis_Knutson wrote:
There are no drivers included with the runtime engine. There is no evaluation period for MAX or license for it. There are no projects associated with MAX. I really don't know what you are doing.

---

You will get a warning if using MAX to work with DAQmx without a LabVIEW development.  I have never understood why.

[Dennis_Knutson]

I have not seen this when using cvi or when a LabVIEW exe is deployed. Is this something recent?

[AGVdude]

---

@Dennis_Knutson wrote:
There are no drivers included with the runtime engine. There is no evaluation period for MAX or license for it. There are no projects associated with MAX. I really don't know what you are doing.

---

Clearly, that makes two of us who don't know what I'm doing.  I will be going back to the original machine today to look for any .lib or .dll files that may not have been copied but otherwise I'm out of ideas short of buying a labview/app builder package and rewriting the whole thing.  Difficult and expensive at best and not possible in the short time I have available to do this right now.   I'd love to take on the task and learn all about it when my time alows.

Thanks to everyone for your input.

[Dennis_Knutson · Accepted solution]

In MAX (Measurement and Automation Explorer), under the file menu, is an option to export the configuration. Select this and create a .nce file. Take this file to the new pc and select import from the menu.

Attach some screen shots of MAX from both computers. Expand everything so someone can see the original setup and what you've done on the new one.

[JÞB]

---

@Dennis_Knutson wrote:
I have not seen this when using cvi or when a LabVIEW exe is deployed. Is this something recent?

---

I first saw this deploying a LabVIEW 2013 exe to a Win7 target that had an expired evaluation LabVIEW license.  (OK, I dropped the 8-Ball license on the machine for integration then deactivated it)  I had stored the Tasks in MAX and imported them.  Tasks in the exe are hard to drive from MAX and the client wasn't a power user of NI products----Scales (offsets for load cells mostly) would need to change and some of the hardware might need to get adds like a new DI for an aux pump that might be needed in the futre.

I left the stuff in MAX so they could futz with it since the main.exe and all the associated utility exe's were designed to handle the changes.

Trying to run a MAX task in MAX with an expired NI-DAQmx MAX Configuration Support (Not default selected as an additional installation even with a MAX config import on install) results in a license warning pop-up.  Build the installer after selecting NI-DAQmx MAX Configuration Support in the additional installation page prevents this pop-up.

NI has been made aware of the unexpected behavior.

[NIquist]

Another option is to simply hire NI or one of the many good LabVIEW consultants to upgrade your application and provide you with a new executable and installer.  Your NI representative will be glad to help set you up.  Not as much fun as buying LabVIEW and doing it all yourself of course.  

[JÞB]

---

@NIquist wrote:

Another option is to simply hire NI or one of the many good LabVIEW consultants to upgrade your application and provide you with a new executable and installer.  Your NI representative will be glad to help set you up.  Not as much fun as buying LabVIEW and doing it all yourself of course.  

---

absolutely excellent advice! I'm not really in the market right now but I can attest certified LabVIEW consultants offer a great way to improve how you code and how you deploy your solutions.  Next to that, the forums are a good resource to get the broad range of advice.  Tailoring a solution for specific business cases takes some experience

[AGVdude]

---

@NIquist wrote:

Another option is to simply hire NI or one of the many good LabVIEW consultants to upgrade your application and provide you with a new executable and installer.  Your NI representative will be glad to help set you up.  Not as much fun as buying LabVIEW and doing it all yourself of course.  

---

Best idea I have heard yet.  I have exausted my options and told the owner he needed to get someone who has experience with this software to help out.  I will pass along the part about talking to NI for a reference.

Thanks again to all who contributed.  I'm done with this thread as it's no longer my project.

Have a great day!

[AGVdude]

This step corrected the device name to the original tag.  The only additional step necessary was to restart the PC after importing the configuration.  After that everything is working now.

Thanks so very much for your assistance.