× 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.



Thanks everyone. The problem was as a few mentioned, that I was passing
in a field from format foordhd.

Thanks all.

Robert Rogerson
On 2011-12-19 1:56 PM, Scott Klement wrote:

Robert,

The "CLEAR FOORDHD" is apparently clearing some global variables.

Is it possible that p_FONumber is viewing the same area of memory as one
of the globals you cleared?

Just because p_FONumber provides read-only access to the underlying
memory doesn't mean that the global variables are read-only, too.

On 12/19/2011 12:06 PM, Robert Rogerson wrote:

Hi all,

I have a subprocedure to create an order header record.
P CreateFlexOrderHeader...
P b
d CreateFlexOrderHeader...
d pi n
d p_FONumber like(ord#) const
d p_BatchIdRec likeds(batchIdRecTemplate)
const

* Local variables

/free
Clear foordhd;
.
.
.
/end-free

P CreateFlexOrderHeader...
P e

When I put the program in debug a break just before the CLEAR FOORDHD
statement the p_FONumber parameter (a new order number) and p_BatchIdRec
(a record used to build a new order record) both have (correct) values.

When I issue the Clear foordhd statement (foordhd is the record format in
the file which I am building a new record for) the value for po_FONumber
is being set to 0 while p_BatchIdRec remains unchanged.

Can someone tell me why p_FONumber being changed?

Thanks,

Robert Rogerson

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.