{
...disambiguates...
}
Larry:
Clearly the word-of-the-month.
An nth-degree of meaning; hardening the squishy "clarify" for utility in
a world of ruthless, heartless code.
kudos,
bruce/safesectors
> -------- Original Message --------
> Subject: [RBASE-L] - Re: retreiving data from variable listview
> From: Lawrence Lustig <[email protected]>
> Date: Mon, March 02, 2009 10:11 am
> To: [email protected] (RBASE-L Mailing List)
>
>
> <<
>
> If you have a variable listview and you select a row, is
> there any way to retrieve the contents of each of the columns into separate
> variables?
> In this case, the the ID returned is not a primary key on
> any table so doing a lookup with it is not an option.
> >>
> Is this a variable LOOKUP listview? If so, you must go back to the source of
> the list view to look up the column data.
>
> Returning an ID that does not uniquely identify your source row is a problem
> for two reasons. First, you can't get back to the original data. Secondly,
> if you have two rows in the list view that return the same ID value, the use
> will not be able to "point" at the second one — selecting it will cause the
> FIRST row with that ID value to be highlighted.
>
> For that reason, in situations like this, I base the list view on a data view
> that creates an artificial primary key that disambiguates the row I'm looking
> at.
>
> Alternatively, you _might_ be able to code this with a custom user-defined
> function that accepts the handle of the list view and a column offset and
> tunnels directly into the Windows list view representation to extract the
> text value of the specified column.
> --
> Larry
