Xailer & OZ Software

I'm wondering why TBrwColumn objects don't have a variable name that can be
assigned (or maybe I don't know how or where to assign it). I can address
them by something like this:
::oDBBrowseGroupAllocations:aCols[1]:aEditListText :=
::oDbfDataSetAllocations:SaveToArray("ALLOC")
but I have to remember which columns hold which data and since just about
everything else has a user-assigned object name, I'm wondering why column
objects apparently don't?
TIA,
Gary S. Rogers

Hi Gary,
Thats an interesting idea ...
It would be nice to have a way of giving them names to get/set their values.
Also the current way of accessing via the array of columns means you can
break your code when you move columns around during development.
I would second this idea..
Regards
Chris
"Gary S. Rogers" <g.s.rogers@att.net> wrote in message
news:48ef92de$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> I'm wondering why TBrwColumn objects don't have a variable name that can
> be assigned (or maybe I don't know how or where to assign it). I can
> address them by something like this:
>
> ::oDBBrowseGroupAllocations:aCols[1]:aEditListText :=
> ::oDbfDataSetAllocations:SaveToArray("ALLOC")
>
> but I have to remember which columns hold which data and since just about
> everything else has a user-assigned object name, I'm wondering why column
> objects apparently don't?
>
> TIA,
> Gary S. Rogers

Hi Gary,
Thats an interesting idea ...
It would be nice to have a way of giving them names to get/set their values.
Also the current way of accessing via the array of columns means you can
break your code when you move columns around during development.
I would second this idea..
Regards
Chris
"Gary S. Rogers" <g.s.rogers@att.net> wrote in message
news:48ef92de$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> I'm wondering why TBrwColumn objects don't have a variable name that can
> be assigned (or maybe I don't know how or where to assign it). I can
> address them by something like this:
>
> ::oDBBrowseGroupAllocations:aCols[1]:aEditListText :=
> ::oDbfDataSetAllocations:SaveToArray("ALLOC")
>
> but I have to remember which columns hold which data and since just about
> everything else has a user-assigned object name, I'm wondering why column
> objects apparently don't?
>
> TIA,
> Gary S. Rogers