After some investigation this morning, I found that you can build a Wait timer in your code, but also found that it doesn't improve the processing speed of the reports, and actually makes it seem like it takes longer (perceived time) as one report is opened and then the next one begins processing. I have determined that it is best to leave it as is and allow all three to process at the same time and then display all three when completed.
However, just in case anyone is in need of the Wait Timer code, here it is ...
Create a Module to store the following code (I called mine basTimer):
Code:
Sub Wait(PauseTime)
Dim Start, Finish
Start = Timer ' Set start time.
Do While Timer < Start + PauseTime
DoEvents ' Yield to other processes.
Loop
Finish = Timer ' Set end time.
End Sub
Then in any of your code elsewhere you simply insert a line to call the timer as shown below:
Since there is no declaration of the PauseTime being Integer, Long, etc. it will accept fractions of seconds as well. During my testing, I was able to enter a .1 in the Call Wait() code and it waited for only a fraction of a second, however that still affected perceived time, which really bothered me. 
The only other warning that I need to offer based on my searches online is that the above code may be affected if run around the time of Midnight. I have seen other postings that refered to Wait Timers they had setup that were affected by the day switch at midnight that caused their code to be in a paused state for a full day. I haven't had a chance to test this (being that it is 8:10 in the morning and I'm not planning on staying up late tonight to test it), so I caution you to use at your own risk!!!