What are the advantages of utilizing a dynamic VI compared to utilizing the VI Call Configuration Dialog Box Reload for each call option?

[sfrosty]

Is it more efficient to use a dynamic VI or utilize the VI Call Configuration Dialog Box which apparently can perform the same function? I realize that there are restrictions on using the VI Call Configuration Dialog Box, however, if my scenario doesn't concern the restrictions, why would I want to go thru the trouble of creating a dynamic VI when I could simply click on the VI of interest and configure from a menu? Are there performance advantages? Thanks in advance!

[tst]

Generally, I wouldn't recommend playing with the call setup dialog at all (for those who don't know it, you can get to it by right clicking a subVI in the BD). By default, VIs are configured to load with callers and that's the correct options for almost all static VIs. The Open VI Reference primitive has multiple advantages:

1. It allows you to select different VIs dynamically.
2. It allows you to spawn multiple copies of reentrant VIs.
3. It allows you to perform asynch runs (although I think that this is something that should actually be available through the call setup dialog).
4. It allows you to open references to VIs in other application instances.
5. In the rare cases where you do want the same functionality that the call setup dialog gives you, it doesn't hide it.