Re: Hex Value for Field+ INFDS AidByte
- From: Jonathan Bailey <jonathan.bailey@xxxxxxxxx>
- Date: Tue, 3 Feb 2009 03:12:54 -0800 (PST)
On Feb 3, 3:04 am, that 1 guy <xint...@xxxxxxxxxxxx> wrote:
gb,
I had this working initially. I only had Auto-Advance on one of the
fields and I refreshed both fields in one pass. I sent the program to
our client and he said it was unacceptable that he needed the screen
to refresh after leaving each field in question. I am already saving
the values before initial load and am comparing them to see if I
perform logic and populate/refresh.
What the client is needing keyed is 3 UPC codes. I'll do my best to
replicate the scenario by showing the fields on the screen.
A = Auto-Advance Field
U = Field Updated by Auto-Advance
n = Some number
spaces = spaces between the fields
SCC UPC (14 digits) A U n AAAAA nnnnn n
UPC (12 digits) U UUUUU nnnnn n
Retail UPC (12 digits) n nnnnn nnnnn n
When the User types the 1st A for SCC and leaves the field the client
wants screen to refresh and logic performed to determine and show the
character ' ' or '0' in the 1st U field (SCC). Then user types the 'n'
and then keys AAAAA and leaves the field it should refresh and show
its value in UPC 'U UUUUU.' Then when they have filled in all the
info and press <ENTER> to then update the file with what's on the
screen.
SCC UPC and UPC share the same manufacturer code (he does not want
the user to type the same thing twice). And for the 1st U field he
does not want his user to have to look at a table to determine what to
type in it based on what they keyed in the 1st A field of SCC.
By the way, thank you for taking the time to address this. It seems
there must be some way to accomplish this. If there isn't then I need
to have enough information at my grasp to tell the client we can't
accomplish as he wants this designed and suggest/sell the client on
another method that will be acceptable for them.
It's sounding like I will need to sell the client on another method
that they will find agreeable.
When I get back to work in the morning I will put some thought to your
suggestions.
peace
that 1 guy
Could you read the cursor position & 'assume' that based on its
current placement whether the user filled the previous field &
triggered an autoadvance? Its far from perfect but most users are poor
at testing so likely would miss it. Alternatively use a function key
for 'update' to replace the existing enter 'function' when the users
are satisfiled. Make it a low Fnumber so they dont have to seach for
shift keys especially if its a handheld device?
Jonathan.
.
- Follow-Ups:
- Re: Hex Value for Field+ INFDS AidByte
- From: that 1 guy
- Re: Hex Value for Field+ INFDS AidByte
- References:
- Hex Value for Field+ INFDS AidByte
- From: that 1 guy
- Re: Hex Value for Field+ INFDS AidByte
- From: gb
- Re: Hex Value for Field+ INFDS AidByte
- From: that 1 guy
- Re: Hex Value for Field+ INFDS AidByte
- From: gb
- Re: Hex Value for Field+ INFDS AidByte
- From: that 1 guy
- Hex Value for Field+ INFDS AidByte
- Prev by Date: Re: Cache error
- Next by Date: Re: Hex Value for Field+ INFDS AidByte
- Previous by thread: Re: Hex Value for Field+ INFDS AidByte
- Next by thread: Re: Hex Value for Field+ INFDS AidByte
- Index(es):
Relevant Pages
|