best way to save large programs

[PaulG.]

I'm running into some problems keeping track of changes I make to a large (500+ vi) application. I have a main program but also call out references to 5 others. All the referenced programs are rather large, too. Should I use a separate llb for each referenced vi? Can I list the referenced vi's in the main vi llb and will the referenced vi load from it's llb? Sorry if I sound confused, but I am. I cannot afford upgrading to 8.0 right now and need to stick with 7.1. Anyone have a fool-proof system? And how can I clean it up right now before I do any more damage?

Paul

7.1/XP

[Dennis_Knutson]

I wouldn't recomend using any llb at all. It takes longer to save a VI stored in an llb, it's possible to corrupt an llb so that no VIs in it are readable, and a source control program that tracks changes for you does not work with and llb. The llb was originally created as a way to save VIs with long file names before windows added that ability and as such, are only useful now as a distribution tool.

[Benoit]

The best way is to keep everithing in order with a good directory tree.

Make some VI Icon with a red bar on top for those that are private and green one for those that are public.

When a part of your application is finish, save it in a backup place and make an LLb could be good. but dont rework VI in that llb.

Benoit