I have noticed a difference in the length of a value of a data control
buffer versus the length of the field it is based upon. If I have a
character field with length 6 and input a 3-character value into the
associated data control, when I check the length of the value of that
control, it is 3, not 6. Is there a way to maintain the original field
length in the data control value?
TIA,
Gary 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.
Length of data control buffer versus length of field
-
g.s.rogers
- Mensajes: 202
- Registrado: Dom Feb 17, 2008 3:35 am
-
ignacio
- Site Admin
- Mensajes: 9440
- Registrado: Lun Abr 06, 2015 8:00 pm
- Ubicación: Madrid, Spain
- Contactar:
Length of data control buffer versus length of field
Gary,
When we start developing Xailer, one thing we were completely sure is to
avoid the ugly spaces on TEdit controls that other products have. I know
that is how CA-Clippper works, but it was only a MS-DOS compiler.
To check the length of a datacontrol:
- oControol:oDataField:nLen
- oControl:nMaxLength
Regards,
--
Ignacio Ortiz de Zúñiga
[Soporte Xailer]
[Xailer support]
"Gary S. Rogers" <g.s.rogers@att.net> escribió en el mensaje
news:[email=48dc36ef@ozsrv2.ozlan.local...]48dc36ef@ozsrv2.ozlan.local...[/email]
>I have noticed a difference in the length of a value of a data control
>buffer versus the length of the field it is based upon. If I have a
>character field with length 6 and input a 3-character value into the
>associated data control, when I check the length of the value of that
>control, it is 3, not 6. Is there a way to maintain the original field
>length in the data control value?
>
> TIA,
> Gary Rogers
When we start developing Xailer, one thing we were completely sure is to
avoid the ugly spaces on TEdit controls that other products have. I know
that is how CA-Clippper works, but it was only a MS-DOS compiler.
To check the length of a datacontrol:
- oControol:oDataField:nLen
- oControl:nMaxLength
Regards,
--
Ignacio Ortiz de Zúñiga
[Soporte Xailer]
[Xailer support]
"Gary S. Rogers" <g.s.rogers@att.net> escribió en el mensaje
news:[email=48dc36ef@ozsrv2.ozlan.local...]48dc36ef@ozsrv2.ozlan.local...[/email]
>I have noticed a difference in the length of a value of a data control
>buffer versus the length of the field it is based upon. If I have a
>character field with length 6 and input a 3-character value into the
>associated data control, when I check the length of the value of that
>control, it is 3, not 6. Is there a way to maintain the original field
>length in the data control value?
>
> TIA,
> Gary Rogers
Ignacio Ortiz de Zúñiga
[OZ Software]
https://www.ozs.es
--
[Equipo de Xailer / Xailer team]
https://www.xailer.com
[OZ Software]
https://www.ozs.es
--
[Equipo de Xailer / Xailer team]
https://www.xailer.com
Length of data control buffer versus length of field
Gary,
When we start developing Xailer, one thing we were completely sure is to
avoid the ugly spaces on TEdit controls that other products have. I know
that is how CA-Clippper works, but it was only a MS-DOS compiler.
To check the length of a datacontrol:
- oControol:oDataField:nLen
- oControl:nMaxLength
Regards,
--
Ignacio Ortiz de Zúñiga
[Soporte Xailer]
[Xailer support]
"Gary S. Rogers" <g.s.rogers@att.net> escribió en el mensaje
news:[email=48dc36ef@ozsrv2.ozlan.local...]48dc36ef@ozsrv2.ozlan.local...[/email]
>I have noticed a difference in the length of a value of a data control
>buffer versus the length of the field it is based upon. If I have a
>character field with length 6 and input a 3-character value into the
>associated data control, when I check the length of the value of that
>control, it is 3, not 6. Is there a way to maintain the original field
>length in the data control value?
>
> TIA,
> Gary Rogers
When we start developing Xailer, one thing we were completely sure is to
avoid the ugly spaces on TEdit controls that other products have. I know
that is how CA-Clippper works, but it was only a MS-DOS compiler.
To check the length of a datacontrol:
- oControol:oDataField:nLen
- oControl:nMaxLength
Regards,
--
Ignacio Ortiz de Zúñiga
[Soporte Xailer]
[Xailer support]
"Gary S. Rogers" <g.s.rogers@att.net> escribió en el mensaje
news:[email=48dc36ef@ozsrv2.ozlan.local...]48dc36ef@ozsrv2.ozlan.local...[/email]
>I have noticed a difference in the length of a value of a data control
>buffer versus the length of the field it is based upon. If I have a
>character field with length 6 and input a 3-character value into the
>associated data control, when I check the length of the value of that
>control, it is 3, not 6. Is there a way to maintain the original field
>length in the data control value?
>
> TIA,
> Gary Rogers
-
g.s.rogers
- Mensajes: 202
- Registrado: Dom Feb 17, 2008 3:35 am
Length of data control buffer versus length of field
I have no problem with that approach as long as I can get the accurate field
length! I am actually VERY impressed with Xailer as I have been able to
accomplish in a couple of weeks what would have taken me months with Visual
xHarbour.
Thanks,
Gary
"Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote in message
news:48dc9782$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Gary,
>
> When we start developing Xailer, one thing we were completely sure is to
> avoid the ugly spaces on TEdit controls that other products have. I know
> that is how CA-Clippper works, but it was only a MS-DOS compiler.
>
> To check the length of a datacontrol:
>
> - oControol:oDataField:nLen
> - oControl:nMaxLength
>
> Regards,
>
> --
> Ignacio Ortiz de Zúñiga
> [Soporte Xailer]
> [Xailer support]
>
>
> "Gary S. Rogers" <g.s.rogers@att.net> escribió en el mensaje
> news:[email=48dc36ef@ozsrv2.ozlan.local...]48dc36ef@ozsrv2.ozlan.local...[/email]
>>I have noticed a difference in the length of a value of a data control
>>buffer versus the length of the field it is based upon. If I have a
>>character field with length 6 and input a 3-character value into the
>>associated data control, when I check the length of the value of that
>>control, it is 3, not 6. Is there a way to maintain the original field
>>length in the data control value?
>>
>> TIA,
>> Gary Rogers
>
>
length! I am actually VERY impressed with Xailer as I have been able to
accomplish in a couple of weeks what would have taken me months with Visual
xHarbour.
Thanks,
Gary
"Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote in message
news:48dc9782$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Gary,
>
> When we start developing Xailer, one thing we were completely sure is to
> avoid the ugly spaces on TEdit controls that other products have. I know
> that is how CA-Clippper works, but it was only a MS-DOS compiler.
>
> To check the length of a datacontrol:
>
> - oControol:oDataField:nLen
> - oControl:nMaxLength
>
> Regards,
>
> --
> Ignacio Ortiz de Zúñiga
> [Soporte Xailer]
> [Xailer support]
>
>
> "Gary S. Rogers" <g.s.rogers@att.net> escribió en el mensaje
> news:[email=48dc36ef@ozsrv2.ozlan.local...]48dc36ef@ozsrv2.ozlan.local...[/email]
>>I have noticed a difference in the length of a value of a data control
>>buffer versus the length of the field it is based upon. If I have a
>>character field with length 6 and input a 3-character value into the
>>associated data control, when I check the length of the value of that
>>control, it is 3, not 6. Is there a way to maintain the original field
>>length in the data control value?
>>
>> TIA,
>> Gary Rogers
>
>
-
g.s.rogers
- Mensajes: 202
- Registrado: Dom Feb 17, 2008 3:35 am
Length of data control buffer versus length of field
I have no problem with that approach as long as I can get the accurate field
length! I am actually VERY impressed with Xailer as I have been able to
accomplish in a couple of weeks what would have taken me months with Visual
xHarbour.
Thanks,
Gary
"Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote in message
news:48dc9782$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Gary,
>
> When we start developing Xailer, one thing we were completely sure is to
> avoid the ugly spaces on TEdit controls that other products have. I know
> that is how CA-Clippper works, but it was only a MS-DOS compiler.
>
> To check the length of a datacontrol:
>
> - oControol:oDataField:nLen
> - oControl:nMaxLength
>
> Regards,
>
> --
> Ignacio Ortiz de Zúñiga
> [Soporte Xailer]
> [Xailer support]
>
>
> "Gary S. Rogers" <g.s.rogers@att.net> escribió en el mensaje
> news:[email=48dc36ef@ozsrv2.ozlan.local...]48dc36ef@ozsrv2.ozlan.local...[/email]
>>I have noticed a difference in the length of a value of a data control
>>buffer versus the length of the field it is based upon. If I have a
>>character field with length 6 and input a 3-character value into the
>>associated data control, when I check the length of the value of that
>>control, it is 3, not 6. Is there a way to maintain the original field
>>length in the data control value?
>>
>> TIA,
>> Gary Rogers
>
>
length! I am actually VERY impressed with Xailer as I have been able to
accomplish in a couple of weeks what would have taken me months with Visual
xHarbour.
Thanks,
Gary
"Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote in message
news:48dc9782$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Gary,
>
> When we start developing Xailer, one thing we were completely sure is to
> avoid the ugly spaces on TEdit controls that other products have. I know
> that is how CA-Clippper works, but it was only a MS-DOS compiler.
>
> To check the length of a datacontrol:
>
> - oControol:oDataField:nLen
> - oControl:nMaxLength
>
> Regards,
>
> --
> Ignacio Ortiz de Zúñiga
> [Soporte Xailer]
> [Xailer support]
>
>
> "Gary S. Rogers" <g.s.rogers@att.net> escribió en el mensaje
> news:[email=48dc36ef@ozsrv2.ozlan.local...]48dc36ef@ozsrv2.ozlan.local...[/email]
>>I have noticed a difference in the length of a value of a data control
>>buffer versus the length of the field it is based upon. If I have a
>>character field with length 6 and input a 3-character value into the
>>associated data control, when I check the length of the value of that
>>control, it is 3, not 6. Is there a way to maintain the original field
>>length in the data control value?
>>
>> TIA,
>> Gary Rogers
>
>