C2016   Name conflicts with previous declaration

     Explanation:  You specified a PRIVATE, PUBLIC, or PARAMETER
     statement containing a variable with the same name as a declared LOCAL
     STATIC, FIELD, or MEMVAR currently within scope.  If you use the /N (no
     automatic procedure) option, this includes any filewide declaration that
     occurs before the first PROCEDURE or FUNCTION declaration.

     Action:  Change the erroneous variable name to another name.