Thanks all for the input...
In the end it was not a "LOCAL" error.? I don't know why the compiler was listing it as such.? Apparently the signal list always shows "LOCAL" in the list regardless if you have any connection under that label or not.? SOOOOOO.... you cannot track "LOCAL" via the signal list or through the modules.
DON'T start deleting modules out of shear frustration looking for "LOCAL" as it is a waste of time and causes endless track and repair issues.
So what was it... (at least in this situation, in my program)
INTERSYSTEM COMMUNICATIONS SYMBOL
I use them to reduce the network load to prevent unnecessary updating to crosspoints.? I don't know if this is the correct usage of this symbol... BUT... what I just learned... if you do a global rename and the label is on an intersystem com symbol... it will update as - undefined.
SOOOO... I had "one" undefined or green line in the intersystem symbol.? The compiler, I guess, is not smart enough to show you this error item so it labels it as "LOCAL" error.
I have a GOOOOOOOOD amount of intersystem symbols so this was indeed very irritating to track down.
There was a clue that I should have seen right in the beginning and if you are reading this trying to track down your issue (in that you fell into the same problem as I had) ... most likely in your compiler error log within two or three lines of the failure error, you will see a connection error of something you don't determine very important to deal with at this time like an end of line instruction (like turn on this light...)? ... open it and it will show fine which mean it "should not be" a compiler error... follow your connections and you will land at the connected but undefined label.? Re-label, go kick your cat,? fart on your dog, and move on.
... again thanks guys for commenting and helping
