Moving project files to another project

[BillMe]

I'm trying to leverage against existing known good VIs in one project by copying them over to another, similar project. I'm using drag and drop from one project window to the other. Unfortunately, LabVIEW wants to create conflicting items in the destination project, e.g.,the source lvlib, shared variables, etc. I can workaround the shared variables, but, in general, what's the "best practice" to accomplish this task? My expectation was that the copied files would be "disconnected" from their source lvlib and "reconnected" to the destination lvlib automatically.

[TCPlomp]

Let met get this clear.

In one project (source) a VI is part of an LVLIB.

In another project (target) a VI is part of another LVLIB (or none).

That cannot happen. The power of LVLIB's is that VI and LVLIB know of each other exclusivly.

To do such a thing I would build a toolkit of the LVLIB's using OpenG builder and place the new lvlib (with another name) under user.lib and load the toolkit in the target project.

Ton

[BillMe]

The two projects are similar in that they have some LVLIBS that are named the same. I am trying to drag a VI from the source project (from "Dynamic VIs.lvlib" ) to the destination project into an LVLIB with the same name ("Dynamic VIs.lvlib" ).

Also found that cancelling the drag and drop "conflicting resources" dialog causes LabVIEW 8.5 to crash ("can't read memory address blah" )

Message Edited by Bill@NGC on 11-15-2008 01:44 PM

[TCPlomp · Accepted solution]

Why don't you drag and drop the lvlib?

Second guess, first drag the VI out of the lvlib in one project just into the project, thus disconnecting it from the owning lvlib.

Save the vi.

Then drag and drop it from the source project into the target project into the lvlib.

Good luck,

Ton

[BillMe]

Actually, I ended up just dragging and dropping and resolving the conflicts, but I like your second idea to disconnect from the owning lvlib before moving to final lvlib in the source.

Thanks.