× 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.



I am not entirely clear on the issue.

You could put an unused one-character input field,
marked as DSPATR(PC ND) at the place om the screen where you want the cursor to actually park when the format is displayed?

Another possible choice is to add push buttons so that the display uses push buttons for the enabled Command Keys?

On 2/26/2013 5:37 PM, Matthew Kelly wrote:
When using push button fields on a screen with no other input-capable
fields, how can I condition the push button field so that it doesn't
inadvertently highlight (because it's the only input-capable field on
the screen) on the first output operation to the DSPF?

Also, is there a way to either hide or protect a push button field?

I'm working on an iSeries running V6.R1 of the OS.





Matt Kelly | Sr. Programmer/Analyst, MED/MC Division

CPU Medical Management Systems | Outcomes Matter

9235 Activity Road | Suite 104 | San Diego, CA | 92126-4440



800-597-0875 ext. 278 Direct

800-597-0875 Office

858-530-2615 Fax

matt@xxxxxxxxxx | www.MED3000.com <http://www.MED3000.com> |
www.CPUMMS.com <http://www.CPUMMS.com>

<http://www.twitter.com/CPUMMS>
<http://www.facebook.com/pages/CPU-Medical-Management-Systems/2314314568
97085>



CONFIDENTIALITY NOTICE: Privileged and/or confidential CPU information
may be contained in this message and may be subject to legal privilege.
This e-mail and any attachments are intended only for the person or
entity to which it is addressed. If you are not the intended recipient
any dissemination, distribution or copying is strictly prohibited. If an
addressing or transmission error has misdirected this e-mail, please
notify the author by replying to it and delete this e-mail from your
system and destroy any hard copy printouts. Any views or opinions
presented are solely those of the author and do not necessarily
represent those of CPU. The recipient should check this e-mail and any
attachments for the presence of viruses. CPU accepts no liability for
any damage caused by any virus transmitted by this e-mail.








As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.