How to build a working executable of the DataSocket writer example VI

[MWI]

I'm trying to build an executable of the "DS Writer.vi" example.  The first problem was that the "DataSocket Server Control.vi" was not distributed with my build/install script.  I fixed that (thanks Dennis) but now I get the following error message.

LabVIEW:  (Hex 0x626) Cannot open a VI with separated compiled code in a Run Time Engine that has no access to the VIObjCache.

There is a solution to that (http://forums.ni.com/t5/LabVIEW/Getting-LabVIEW-load-error-code-59-using-LabVIEW-2010-with-a-Run/td-...), but it involves changing a property of a VI in the DataSocket library (if I understand that correctly).  I'm reluctant to make a change to a standard NI library as it could cause maintenance problems in the future (other developers not having the same change, or updating LabVIEW versions).

Has anyone successfully built an executable using DataSocket?  If so, can you offer any advice?  I'm using LabVIEW 2011.

Thanks, Mark

[NathanS]

Hi MWI,

I am sorry to hear you are having this problem. I can see that you have done a thorough search of the available resources, so you've probably already seen the following article, but just in case please have a look at:

http://digital.ni.com/public.nsf/allkb/4490B8AD76E0410F86257093007110EC

Regards,

[MWI · Accepted solution]

Thanks Nathan.  I was able to build and deploy an executable with DataSocket.  The last hurdle was to "Uncheck the 'Separate compiled code from source file' option in VI Properties" for the "DataSocket Server Control.vi".  The only problem with that solution is that I now have a customized DataSocket library.  I think one solution might be to copy that VI or the library into my project folder so that the solution is transferrable to others in the future.  I would like to hear how other LabVIEW developers deal with customized libraries, either by strictly avoiding that, maintaining their own copies, or some other solution.  But that is probably a topic for a new thread.