Yes!
You almost had it.
Watch the VI Hiarchy screen when you execute your code in execution highlihgting mode.
You will see that you VI is being unloaded before the chages are made.
I have modified your code, see attached.
The big difference is I have added a shift register that caches the VI refnum. THis keeps the VI in mememory once it is loaded.
I removed the close VI refrernce from the load event.
Moved the read from controls into the event that use them and added one local to make up the difference.
I alos added an explicit save event to save the VI. This works as long as nobody else is using it.
If you really want to have fun, try adding an additional load to your program and add a typedef to the FP of the "VICTUM.VI".
By renaming typedefs and control load order, you can re-define the objects on the FP of VI's.
I hope this helps,
Ben