×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hi Ken,
I have the task of stripping a numeric field from a record , the length
of the field is either 6, or 7 or 8 or 9 or 10 numeric digits in length
Not sure precisely what you mean by this, but the LBCPYNV MI builtin can
be used to copy a numeric field in one format to another without needing
to know the sizes at compile time.
Not sure if that's really what you're trying to do, though?
The SDA/greenscreen field entries, (unlike input boxes , and internal
field definitions in applications like VB), generally specify a specific
length for the field
You can use the Dynamic Screen Manager APIs to create fields on a screen
where the sizes of the fields are only known at run-time. You can then
use LBCPYNV (as suggested above) to copy the field value from the screen
buffer to a variable in your application.
So, the screen field size would be controlled by variables, and the field
that you read it into in your program would be defined as the largest
possible size for the field, to make it easier to work with.
Does anyone have the code snippet to handle this type of variable
input?, obviously an array process.
Maybe? I'm not exactly sure what you're trying to do. Are you trying to
remove a field from a record ("strip" it) so that the record now exists
without the field? Or are you trying to display a variable-length number
on a screen? or are you doing something with arrays? (I didn't
understand the "obviously an array process" at all... what on earth does
this have to do with arrays?!)
Please clarify your situation, and I'll check to see if I have any code
samples that are close.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
