× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi,

I had to modify a module that manages a customer screen to make it display slightly differently depending upon the kind of transaction on the customer.

I had a transaction code to pass to a procedure in that module. As so many other procedures also called that procedure, I wanted to avoid adding a parameter. If I'd used *NOPASS, I would still have to have passed that parameter through several other procedures in the module before getting to what I wanted to do.

I created a procedure SetTransactionCode in the module and simply called SetTransactionCode from my calling procedure to initialise a new global variable in the module. I then used that variable to set indicators for the display file.

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.

Any opinions?

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.