Better to keep similar LV8 projects separate or combined?

[GS]

I have several LV8 projects that relate to the same task, e.g., one set of VIs deals with data acquisition and another set deals with data post processing. I create separate executables for each of those tasks. Some VIs are common to both tasks. I'm wondering if it's a better practice to keep everything in one project or make a separate project for each task. I've tried it both ways and so far I think making separate projects is overall less confusing. Is there some unseen advantage to keeping everything in one project that I might be missing?

George

[Kenny_K]

I have been dealing with the same dilema.  I am along the thought process that seperate projects is better.  I even went a step further and renamed the files for each project (thermocouple for time response, thermocouple template, etc).  That way if I wanted to change the VI to add something, I was running the risk of it changing all my other projects.  Another reason for this is I tried keeping my project files seperate, so I would have the same files in multiple locations and the project would sometimes pull the VIs (same name) from a different project folder.

Kenny

[Justin_M]

Projects were added into LabVIEW 8.0 as a way of managing very large programs, which can contain multiple VIs, variables, etc.  From an efficiency standpoint, using a project will not make the LabVIEW code itself better or faster.  However, there are many benefits to using a project library, as explained in the following documents:

Managing Large Applications with the LabVIEW Project

Sharing Code with the LabVIEW Project Library

That being said, creating a separate project file for each of your standalone applications (executables) seems reasonable to me.  I would suggest organizing your application in any way that is most intuitive to you.

-Justin

[GS]

Thanks for the thoughts and the links. I hadn't seen those yet.