@ dodicat
Your comments sent me in the right direction and am back to where I was a few years ago, working with Geany with no problems - other than awkwardness you allude to. Let me describe the steps I take and what I observe. I am calling the starting program used file.BAS which executes with Geany and is fully executable. The permission codes are essential, they work, thoh may not be coded perfectly.
Here goes:
Definitions:
fully executable – program runs and initiates meters for data(volts) capture
partially executable - program runs, but does not initialize meters for data (volts) capture
Geany
open it with no programs
Desktop
file.BAS(fully executable) copy to (copy).BAS
change name to copy.BAS
Geany
open copy.BAS
run copy.BAS – get error msg, does not run
compile copy.BAS ---> copy.EXE on Desktop
run copy.BAS – runs, BUT is only partially executable
close Geany
Desktop
run copy.EXE – runs, BUT is only partially executable
Terminal
cd Desktop
sudo chown copy.EXE
sudo chmod -R -f 4777 copy.EXE
exit terminal
Desktop
run copy.EXE, fully executable
Geany
find it empty, no programs
open copy.BAS – fully executable
So, I am very happy to be programming again without aggravation wrt Geany. However, considering fxm's input and your comments, I ask the following: Am I correct that after I have done the above, then make changes to copy.BAS in Geany, that when I run the .BAS in Geany it is actually compiling it behind the scenes before running it, thoh it appears to be running as copy.BAS?
[edit]
And this morning the "Coup de Grace". I deleted the copy.EXE from the Desktop, then went to Geany and tried to execute copy.BAS. Sure enuf, it would not execute and generated the error msg. Just what you said: the compiled program must be "present in the background" in order for the .BAS to work in Geany. It does seem like strange behavior.
