@BrettW - THANK YOU!! That did the trick. I did not realize what I had to do that - put the clear statement just before. I will try to remember that. I have been having to fudge things for the last while to make the analog inputs read correctly for the last couple of projects I have done. Thank you.
@Coding Badly: Thank you for making the clear statement clear with your example.
Also of great interest is your comment on "pin 5" is something I've been wondering about for a long time (weeks) - how does the Arduino IDE know if a pin assignment is "pin 5 - Analog (m168 pin 28)" or pin 5 - digital (m168 pin 11)"?
I work with the m168 pins and have to refer to a the Arduino pin mapping to help keep pins straight. Most of my projects use a home etched PCB with the m168 installed.
Can you - or anyone - shed light on how the IDE keeps those pins straight?
AND a BIG THANK YOU to all the folks who make this a GREAT group.
Ken H>