Thx warwound and Erel but I am a bit confused: whenever one creates a new static code module the IDE creates a template for the module with a
Process_globals section at the top. I did as warwound had suggested in my TestPgm. I uncommented out the Process_Globals section in the CommSubs static code module of TestPgm and the compiler error went away. In the actual project which I am developing, I had removed this section altogether from my CommSubs module assuming that since I only had ONE activity in my project and that all of my globals for that activity need to be declared in the 'main' module. I have not found anything up here to suggest that multiple Process_Globals sections are required in order to reference globals defned in main and assumed that I could remove that section altogether from additional static code modules even though the IDE put them there from the get go.
Anyways, I added Process_globals section back to my "real" project and NO COMPILER errors anymore so now I can begin to split off all of the subroutines from main back into CommSubs since things will now work.
If one needs a Process_Globals section in static code modules what would you put there and how would you reference them if you only have ONE Activity? I come from over 30 years of C/Assembler programming background where I would declare all constants and Globals in one module and not have them all scattered about in my applicarion. All constants are given names and assigned a value, This is good programming practice - I name all of my constants and never declare (i.e Timer_interval = 1000, etc.)them in subroutines scattered throughout the code. If One needs to change a constant he does not have to look all over the place in the code. It is changed in one place and all references are updated from that central location
So I am assuming the multiple Process_globals sections issue might/could be a compiler bug right now and not worry about it for the time being. I ran into something else the other day where I had mispelled a variable name and the compiler did not pick it up at all. As I recall, it was not a matter of an upper/lower case issue - the variable was totally spelled wrong and the compiler ignored it totally . I should have documented it right away and reported it but instead fixed it,
My first project is getting larger now - near 1500 lines involving files, encryption, splash screens and probably will use every library available here LOL before it's completed. This will be my first real app so i might as well dive in head first to learn the language. This is how I've always learned a new language - pick a project and then pick and learn the select language to complete it. I don't know SQL and that will be coming soon too. I love B4A so far and looking forward to start coding the next dozen or so I have on the back burner once this is released to the Market. Hopefully, I will be considered an "expert" by then! BTW I am using v1.7 instead of 1.17 as I had initially reported.
thx for your help. Maybe you others here can benefit from my discovery.
-Ray