declare global error

[Dennis Malen]

Thanks so much for the suggestions. Have not been able to get to our server
yet. Will do so shortly and test. I am sure that one of them will work. Will
let everyone know which one in order that everyone else can hopefully learn
something from my experience.

Thanks again, most appreciated.

Dennis

-----Original Message-----
From: Kenneth Brody [mailto:kenbrody at spamcop.net] 
Sent: Wednesday, November 07, 2012 10:04 AM
To: Dennis Malen
Cc: 'filePro Mailing List'
Subject: Re: declare global error

On 11/6/2012 8:18 PM, Dennis Malen wrote:
> I am getting the following error:
>
>    ERROR  Global 'sandy' already defined.
>
> I have a call statement in @entsel.
>
> In @entsel I have a "declare extern sandy"
>
> In the call statement I have "declare global sandy(8)"

I assume you mean in the call *processing*?

> Any reason anyone can see why I would be getting an error.
>
> Sandy is not defined anywhere else in input processing.

Are you assigning a value to "sandy" in input processing prior to calling
the processing with the "declare global"?  If so, that's the problem, and
you'll need to put the "declare global" in the input processing.

filePro will allow you to make the assignment to a variable that, so far,
has only been declared "extern", and gives it a tentative definition based
on that value.  However, unless the value assigned to it matches the
definition in the eventual "declare global", the tentative definition and
the "real" definition in the "declare global" won't match, and you'll get
the above error.  (So, in the above instance, if you were to assign an
8-character value to sandy, you wouldn't get the error.  However, you'd only
be hiding the fact that there is a problem.)

--
Kenneth Brody