Help with building LabVIEW code

[Program Spartan]

OK, I have used LabVIEW before but I'm still learning the software. I know how to use the coding techniques but one problem I have always had was building the code onto the cRio. What confuses me is what should I do to build the code. I know you have to use the build specifications option and run the robot main but for some reason, it is not allowing me to use the code for the robot. From the Driver Station, it tells me that the code is starving or there is too much when I run the coding. When I run teleop, the coding is there but I cannot move the robot. My team has used this robot during competition and it worked fine. The only problem was when I tried to use an additional motor, two solenoids, and a compressor, they would not work.
So here are my questions:
1. How can I build coding onto my robot without having to lose the data once the cRio turns off? What is the procedure?
2. What am I doing wrong with the coding?

To clear up the robot's purpose:
For the Ultimate Ascent Challenge, we made a canister to hold Frisbees. In the canister, near the bottom of it, is a solenoid that is suppose to extract once a boolean is pressed and retract once released (used to hit the Frisbees). Of course we use a compressor for air. The coding for it is in the periodic task. It is then launched into a spinning wheel to launch the Frisbees. The wheel is being controlled by a boolean. The main robot drive is operated in arcade drive and talons are being used. Take note, the first joystick is used for driving and the second one is used for shooting the Frisbees. And I have also placed a Wait(ms) function in Robot Main. Additional pictures will show the manipulated coding that I have placed in the project.
Any type of help would be nice.

[Program Spartan]

[kgzak]

I am currently mobile so I can't check your code but to keep the code on the cRIO all the time you have to run it as a startup. In the project window where it says build specifications you have to right click and select build. Then you right click and select run as startup.

[Mark McLeod]

You should not make any changes to Robot Main.

Remove the delay that you added to Robot Main.
That is stopping your robot from working correctly.
It prevents your robot from responding to the driver controls for that amount of time (200ms).
When the main drive motors do get an infrequent driver command (1 out of every 10), they will "stick." Luckily they will then be shutdown after 100ms by the motor safety you Enabled in Begin, so you might see random jerky twitching that stop as soon as they try to start.

The Motor Set Output expects values of -1.0 to 1.0.
In Teleop and Autonomous the values 300 & 255 will be interpreted as 1.0
I hope you are using zero somewhere to turn it off.

In Autonomous, what are you doing with the output of the Wait to the Case? I assume you have time Cases for flipping the single solenoids?

[Program Spartan]

@ kgzak, thanks for the input I will see if it would work tomorrow.
@ Mark, I was attempting to use the solenoids to shoot out about 3 Frisbees from the canister at a every 5 seconds for 15 seconds. Bear with me, I'm not so good at autonomous.

[Program Spartan]

And I have also made sure there was a 0 input for the motors.