Selecting to a list variable is a VERY good idea. Personally, I regard
selecting to the default select list in a program as very bad form, and
using a numbered select list as only marginally better. Brian Leach's
response has a good explanation of why, so I won't go into details.
I'm not aware of any additional overhead, and can't imagine why there
would be any, but I am not familiar with the implementation details, so
I can't say authoritatively that there is none. I guess that some
memory would need to be allocated to manage a list stored in a list
variable, whereas it would already be allocated for the default list,
but we're talking about clock cycles here. In practice, I know of no
viable reason not to use list variables.
[EMAIL PROTECTED] wrote:
Hi all,
Can someone tell me the diference between the following two examples of
executing an external select?
SELECT FILE TO LIST
LOOP
READNEXT ID FROM LIST ELSE ID = @AM
UNTIL ID = @AM DO
REPEAT
SELECT FILE
LOOP
READNEXT ID ELSE ID = @AM
UNTIL ID = @AM DO
REPEAT
Someone pointed out to me that there is overhead in selecting to a list that I
need not be exposing myself to. Aren't they both kind of reading from a list
somewhere anyways?
Thanks
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
---
[This E-mail scanned for viruses by Declude Virus]
---
[This E-mail scanned for viruses by Declude Virus]
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
