‎06-30-2009 02:22 PM
‎06-30-2009 02:33 PM
‎06-30-2009 07:23 PM
‎06-30-2009 11:01 PM
I have no idea why your company does not own the source code. You would have to look at the agreement between your company and the vendor. It's sort of like asking why you don't have the source code for Excel. Somewhere, someplace, they may have provided the C source code but without it, there is nothing you can do to modify it. When the CIN code is compiled, it is the compiled code that is loaded into the CIN(the Load Code Resource option when you right click) and there is no need for any external file.
A CIN is different than a Call Library Function Node where you are calling a dll. A dll is a library with function prototypes.
‎07-01-2009 02:53 PM
I think we had a misunderstanding.
Since I don't see any evedence of source code, or any code (even a name, or description), for that matter, for this CIN (it is a CIN and not a Call Library Function Node) I was assuming it could have been written by someone else (possibly sold to us by another company with or without source code; if this were the case then there should at least be a description somewhere) and not available to me.
For this discussion let's assume that someone in my company wrote the VI and the CIN within the VI. Shouldn't the source code be available for me to review and/or modify? Is the source code just thrown away?
I guess I'll just try a test: Creat a VI with a CIN; write some simple source code; save it; then see if I can access the source code again, somehow.
‎07-01-2009 03:08 PM
If the CIN was created by someone at your company, you would need to find out who created it, when it was created, and where the source code was saved. I would think you would be familiar with the storage of code developed internally. If it was internal, that process is one you have to find out. Once loaded, the source code can be deleted and though it would be a dumb idea, it has happened. The source code could have only existed on the original developer's pc. Once deleted or archived, the CIN alone is distributed. It's no different than any other code development if you are at all familiar with that.
You also have no way to know whether the CIN was developed internally or by a third-party.
Also, your test is meaningless since you can always access the source code until you delete/archive it. Instead, create a CIN with the source code locally and give it to someone else. Assuming that there were no mistakes, see if the other user can find the source code. Unless you grant the other user access to your pc, how can it be found?