Keep going if reportGen encounters a string variable

Old behavior was to raise an uncaught exception. Now it reports a warning and continues onward.