>The thing worked great as is, I added a few routines, the thing still
>worked and compiled great. Week later I changed a single PICTURE FIELD
>attribute from _noFramed to _noFramedNOCR (no click reverse), saved,
>recompile the Include, and suddenly, I get an error message that

When I've seen strange things like this, I usually suspect a 
"non-printing character" somehow has gotten imbedded in the offending 
line.

I open the file in BBEdit Lite and tell it to "zap gremlins", turning 
them into an option-eight "ball" character. Usually it finds one in the 
line with the weird error, I delete it and resave, and everything's 
fine...

Typically this will happen when I've got a routine that's trashing memory 
and I run from within FB (it overwrites the source file that's in 
memory). So the character itself doesn't fix the _real_ bug, but gets me 
beyond that point where I can start looking for the real one.

Bill