What you describe is the nature of the beast. It works that way across all your applications. If you are successful in changing the pattern will you have created inconsistency for your users?

A solution that might tend in the direction you are going is to use the Windows model and have just one or two fields/screen and have the user navigate through the fields with screen after screen. It sounds clumsy, but it may not be clumsy in your scenario.



Alan Shore wrote:
Thanks for your reply Dave. I think what you are talking about is
CHECK(ER).
I do use this, however if you re-read my example, the cursor is NOT at the
end of the field. That's my predicament.

Alan

midrange-l-bounces@xxxxxxxxxxxx wrote on 09/01/2006 02:27:16 PM:

Actually, there is a possibility of making the block oriented data
stream work something like what you want. It's been a long time, but
there is something you can put into DDS that tells the system to do an
auto-Enter type of action. If you were to put that on each field, as the
user went from field to field, the display would return to the program.
You would then determine what field was entered, if it was correct or
not, and re-write the screen with the cursor placed where you wanted it
to be.

Don't know if it's practical, but I have used it in the past. Primarily
on the last record of a subfile used in heads down entry. When the user
hit the last field, the screen would automatically refresh and the user
would be able to continue entry with no hesitation - OR - keying over
information already entered...

Spoz that could stir up a bee's nest maybe... :-)

Dave

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Friday, September 01, 2006 1:25 PM
To: Midrange Systems Technical Discussion
Subject: RE: Field filled in


Charles - thanks for your reply.
When you say "It sounds like you may be wanting something to occur while
the user is typing", that is correct, and I realize that would be almost
impossible, BUT some past questions that have been posed, I have thought
of as being impossible, this e-mail group has proven me to be wrong too
many times for me not to consider posting this question.

Alan

midrange-l-bounces@xxxxxxxxxxxx wrote on 09/01/2006 01:00:39 PM:

Alan,

Not sure I understand the question.

Seems like the answer is a simple if statement:
if %subst(dspFld:%size(dspfld):1) = *BLANKS;

But I'm guessing that may not be what you are after.

If sounds like you may be wanting something to occur while the user is
typing.  That would be almost impossible as the 5250 data stream is
block oriented.  Until the user presses enter or a CA/CF key, the
iSeries doesn't see anything.  Stream oriented terminals on the other
hand send every key press to the server.

Consider moving your app to the web and using AJAX, it would be well
suited to processing while the user is typing.  (This is the way
google
works)

HTH,


Charles Wilt
--
iSeries Systems Administrator / Developer Mitsubishi Electric
Automotive America
ph: 513-573-4343
fax: 513-398-1121


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Friday, September 01, 2006 12:51 PM
To: Midrange Systems Technical Discussion
Subject: Field filled in


Hi everyone.
I have another question for anybody.
Within DDS, is there a way to tell if the last character of a field
is NOT blank.
Let me try to further explain with a simple example.
Lets say a 25 character field, DSPFIELD, contains the value


JUST AN EXAMPLE
which is 15 characters long.
The user then proceeds to fill in the rest of the screen, and later
returns to the field DSPFIELD and INSERTS data in the middle of the
text to change it to

JUST YET ANOTHER SMALL EXAMPLE

This now fills in (and more) the 25 character field.
Obviously, in real
life, the insert would have stopped when the second E in EXAMPLE
filled in the 25th character. Apart from the user NOT being able to
insert ALL the text, is there a way for the program to realize that
the last character is NOT blank.
P.S. don't forget, in my example, the cursor would NOT be in the
25th character.

Any help/suggestions greatly appreciated.

Thanks in advance



Alan Shore

NBTY, Inc
(631) 244-2000 ext. 5019
AShore@xxxxxxxx
--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



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.