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
In order for this site to work correctly we need to store a small file (called a cookie) on your computer. Most every site in the world does this, however since the 25th of May 2011, by law we have to get your permission first. Please abandon the forum if you disagree.
Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.
Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.
TBrwColumn objects
-
g.s.rogers
- Mensajes: 202
- Registrado: Dom Feb 17, 2008 3:35 am
-
ChrisGillard
- Mensajes: 384
- Registrado: Mar May 01, 2007 5:49 pm
TBrwColumn objects
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
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
-
ChrisGillard
- Mensajes: 384
- Registrado: Mar May 01, 2007 5:49 pm
TBrwColumn objects
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
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