LabVIEW
Tab control only allows two page selections
Does not look like your event structure are in a while loop, meaning once the execute once, they will never execute again during the same run of the program.
I would recommend to only use a single event structure. You can add several event cases to handle all your events.
(Of course we canot see the entire code, so please attach the VI if this does not solve your problem)
WOW,
you realize that two of your event structures are running in parallel with the while loop- and they will only execute once? One event- one event execution event. The construct "finishes" done! it won't look for another event.
Take a look at the shipping examples or the P-C QSM (events) template.
Your efforts are not bad, but, show a lack of LabVIEW basics- Dataflow is a different Paradigm- (AND REALLY POWERFUL) but you do need to understand what happens when you use constructs that "break data flow" like locals, globals, and event structures and read the caveats in the LabVIEW help file to get grounded in "best practices"
CAVEAT:
I've probably "broken" most of the "best practices" guidelines- Intentionally! but I wanted specific things from LabVIEW that I knew would happen without race conditions. 99.995% of my code does not violate the "best practice" rules. I write a lot of LabVIEW- It gives me room in that 0.005% to do "interesting" things. 
There is a more efficient way to enable all your pages than what you are showing on the left side of the program. Instead of essentially duplicating the same code 4 times, just use one instance. Get rid of the Index Array and feed the array of references into a for loop with autoindexing enabled.
Advantages: 1. Less code. 2. If you later add another page, you don't need to duplicate all the code again to enable that page. The reference to it is already in the array.
