Re: Procedure to set global variable

[Ken Sims <mdrg8066@xxxxxxxxxxx>]

Hi David -

On Tue, 6 Oct 2009 16:20:53 +0200, David FOXWELL
<David.FOXWELL@xxxxxxxxx> wrote:

> I now have a further modification to make to this module, and I am wondering if I should change what I did before. I am a little worried about this. It's like I've created a side door where one can come in and mess with global variables.

Personally, I would just leave it as a global variable.

But another way is to make the SetTransactionCode procedure a SetGet
procedure.  Make the transaction code parameter *NOPASS.  Add a return
value for the transaction code.

When passed a transaction code, that value is saved and also returned.

When not passed a transaction code, the saved value is returned.

Then the transaction code can be saved in a STATIC variable local to
the SetGet procedure.

Ken
Opinions expressed are my own and do not necessarily represent the views 
of my employer or anyone in their right mind.