|
> -----Original Message----- > From: rpg400-l-bounces@xxxxxxxxxxxx / Tim Kredlo > Sent: Thursday, September 09, 2004 3:11 PM > > Thanks for the suggestions. > I was looking for a convention that would be easily reusable, maybe a > service program, and your methods looks like something I could use. > > The mapping of field locations for row/col does seem like way too > much work, especially for program maintenance. > > I guess of all of the attributes I would NOT want to define in > the attribute field, cursor positioning would have been way down > the list, if on it at all. > Oh well! Maybe I mismember, and I'd look it up but I'm short on time today, but isn't there a DDS keyword with a p-field that lets you specify the name of the screen field that you want the cursor positioned to? It would obsolete the need to use DSPATR(PC), and then you could use the DSPATR(p-field) solution. hth, db
As an Amazon Associate we earn from qualifying purchases.
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 copyright@midrange.com.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.