Applet won't proceed past "activate" command

Question

I am unable to work around this any longer.
I have a script saved as an application bundle:
(*BEGIN SCRIPT FOR APPLET 1*)
set BA_ to ((path to me as Unicode text) & "Contents:Resources:BeepApplet.app")
beep 3
display dialog "Okay, this dialog shows.  But will the one AFTER the activate command show?"
tell application BA_ to activate --should cause another 5 beeps, and probably will
--But will the following dialog show?
display dialog "Foiled Again?"
--THE ANSWER IS NO!
(*END SCRIPT FOR APPLET 1*)
As you can see, the applet contains a second applet (in the bundle, but it could be anywhere if its path is properly specified).
When the second applet is called (tell application BA_ to activate), the second applet does its thing properly (provides another 5 beeps), but for me the first applet won't proceed past the "activate" command.
I've tried calling application BA_ in a variety of ways, but always seem to get the same result.  Is this normal behavior?  Is there a way around it?
(Here's the very simple underlying script for application BA_:
beep 5)

Answer 1

Please see my response to red_menace.  I've indicated that both your and his response were "helpful"
It appears that my response to red_menace has disappeared.  Basically, it provided a version of the applet script that seems to work;
(*BEGIN REVISED SCRIPT FOR APPLET 1*)
set BA_ to ((path to me as Unicode text) & "Contents:Resources:BeepApplet.app")
beep 3
display dialog "Okay, this dialog shows.  But will the one AFTER the launch-run command show?"
tell application BA_ to launch
tell application BA_ to run
--But will the following dialog show?
display dialog "Foiled Again?"
--THE ANSWER IS (it seems to)!
(*END REVISED SCRIPT FOR APPLET 1*)
I also experimented with the load script/run script approach; while promising, it wasn't suited to my purposes.