C2016   Name conflicts with previous declaration

    Problem:  A PRIVATE, PUBLIC, or PARAMETER variable has 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 file-wide declarations that occur before the first
    PROCEDURE or FUNCTION declaration.

    Solution:  Change the erroneous variable name to another name.