Here is my Global Code section:

// Global Code
Stat sComboColor as String
Stat sComboSize as String

sComboColor = "Red;Orange;Yellow;Green;Blue;Violet;Black;White;Brown"
sComboColor = @SortStringArray(sComboColor, 0)
PopulateListElement(Color, sComboColor)

sComboSize = "Micro;Tiny;Small;Medium;Big;Large;Huge;Gigantic"
sComboSize = @SortStringArray(sComboSize, 0)
PopulateListElement(Size, sComboSize)


SubRoutine srFailed(vFlavor as String)
@MsgBox("This does combine with a " + vFlavor + "flavor.","It will be Yucky!","")
End SubRoutine
 

====================================
When testing, I get the following error:
Error while parsing module " GLOBAL CODE ";
Statement or End-Of-File expected.
Line 23, position 1: SUBROUTINE
Subroutine srfailed(vflavor as string)
-------------------------------------------------------

I get the same error for any SubRoutine, I tried this smaller one with the same result.

SubRoutine MyTest()
	@MsgBox("Test","","")
End SubRoutine 

What can be wrong in the earlier sections that prevent me from entering a SR?  If I move the SRs to the top before declaring the stat variables, I don't get the error.  It looks like there is a sequencing order for variables, sub routines, code lines?  If Yes, what are the rules, and where is that noted in the documentation?

Thanks Ray.

But in my original layout, as shown in my example, the declarations were first.
That was followed by initialization of the variables, some programming code, and then the subroutines.  That seems to be no different from what you are saying except you are putting SR before programming code and initializations.  What am I missing here?

Subroutines and Functions are also declarations.

AHA!.  Thanks, now it is so obvious.  You're the man