×
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.
That's true, CTDATA must be global to the module. That's one
disadvantage to it.
There's no problem with referencing CTDATA in a procedure -- it's no
different than referencing any other global variable in a procedure.
But I do see the disadvantage of it being global. Thanks for reminding me.
That's not a problem with INZ, though... you still haven't told me
what's wrong with Jon's technique?
On 4/1/2011 5:41 PM, Alan Campin wrote:
Unless I am mistaken CTDATA has to be defined globally meaning defining
static storage. An INZARRAY or
defining like I did means it is defined locally. Also didn't I read you
cannot reference CTDATA in a subprocedure?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.