Yair

There are properties in the Numeric class for FXP settings, but they appear to be private. See the floated thread in this forum for information on private properties.

One good reason to separate is that recompiles still happen in released code (change platform/bitness/version etc.) and if you don't separate, LV will show your VIs as modified unless the installer resaved them after install (which VIPM is supposed to do if it's configured to, but didn't always work). There are also cases where VIs occasionally decide they need to recompile for no apparent reason (VIs which have ActiveX calls are particularly bad at this - they decide they have a different component from the one they had before).

The orphans thread was in the BreakPoint. On LAVA you have this thread - http://lavag.org/topic/10729-labview-idea-exchange/

Once a VI is reserved for execution (or running, which is the same thing practically) the selection list is always cleared - selections only exist in edit mode. To use the Selection List[] property, you have to open a reference to a VI which is in edit mode, which you can do by using either the Open VI Reference primitive or the New VI primitive, which will create a new VI. The property is very useful for performing operations on the selected items.
 
Attached is the template I usually use if I want to write some quick code for manipulating multiple objects (LV 2009) - it get a reference to the VI you're working in. I believe it was a quick mod from something Norm posted.
Scripting.vit