Joe S.,
Interestingly, when I copied this code int a Workspace project I created in MPLAB with PICkit2 set as programmer and PICBASIC Pro set as language, it compiles without any errors and will program into the PIC16F690 via the PICkit2 programming interface. It work as advertised this way.
However, if I copy the same code into MCS and try to compile it (with the PIC16F690.incl either normal or edited per you instructions) it creates all of the same 113 and 118 errors about not licking the symbols or overwriting....the original problem I observed.
I wanted to use the MCS/PICkit2 programming environment, but if I can't get it to compile the programs I will just have to use the MPLAB environment setup to operate with PICkit2. The reason I wanted to use MCS is because of its context help feature on PICBASIC syntax. I guess I can still write programs in MCS and then copy them into a Workspace on MPLAB for programming, but this is extra steps I wanted to avoid.