×
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.
On 22/01/2009, at 9:24 AM, M. Lazarus wrote:
Does that mean that the entire screen must be generated via
DSM? Or can I retrofit this in combination with standard DDS?
The message is fairly clear. In order to use QsnSetCsr with a Field
ID you must previously have defined that field with QsnSetFld. All
this really does is map a field ID to row and column co-ordinates to
make it easier to reference such a field later.
Because you are using DDS to define your fields DSM has no map of
Field IDs to co-ordinates hence the error message. You'll have to use
row and column values on the API.
Your code will have to provide the mapping of fields to co-ordinates.
You can either hard-code the relationship in a dimensioned data
structure or use the QUSLFLD API to list the fields in the file and
extract the row and column numbers from the populated user space.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
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
