saving a record in the middle of data entry
Richard Kreiss
rkreiss at verizon.net
Sat Jul 3 10:14:05 PDT 2010
> -----Original Message-----
> From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com [mailto:filepro-list-
> bounces+rkreiss=verizon.net at lists.celestial.com] On Behalf Of Mike Schwartz
> Sent: Friday, July 02, 2010 12:38 PM
> To: filepro-list at lists.celestial.com
> Subject: saving a record in the middle of data entry
>
> Using filePro 5.0.14 and SCO Unix 5.0.7, I designed a very tightly
> packed data input screen that looks like a mini-spreadsheet. There are 32
> rows or 6 fields in each column (16 groups of 6 on the left half of the
> screen and 16 groups on the right half of the screen).
>
> I realize that this is a lot of data entry for one screen. I'm worried
> that users might get part way through the screen, then lose all their work
> if their internet connection drops.
>
> I'm would like to set up some kind of "save" routine that will execute
> at certain points as they are doing data entry. I could execute this save
> routine using something like @wef after every few columns of data entry.
>
> Before I reinvent the wheel, do any of you have any pushkey routines or
> other ideas that will allow me to save the record periodically and then
> return the users to the same spot on the screen with the least amount of
> interference in the data input?
>
> I'm also considering copying the screen periodically to an archive file
> or some such thing. I just need a method that will be relatively fail-safe
> if a user's internet connection drops.
>
> These screens will be used in fairly high volume data input, where I
> expect the users to get quite proficient in data entry, so I want to
> minimize the time delay or other user interference during this "save"
> process. The high volume of data entry is what is prompting me to put so
> many data fields on one screen, so that the users don't have to press
> "esc-esc" so often and can see the column totals and compare them to the
> totals on their 32-line data entry sheets before they press "esc-esc".
>
> I've reviewed some of the pushkey suggestions from past emails, and I
> see that there are some good ideas there. If I don't get any other good
> ideas, I'll try writing something based on those ideas.
>
>
> Thanks!
>
> Mike Schwartz
Mike,
filePro has the ability to change screens so that the user never has to exit out, change screens and then update.
I had one application which used 12 screens for entering data. Using @wlfxx on the last field of the screen,
Screen n,f this moved the cursor into the first field on the next screen. To allow backing up, I added:
◄ If: @sk="LTAB" or @sk="UTAB" or @sk="CRUP" or @sk="CLFT"
Then: SCREEN n,fl (previous screen last field)
This allowed a user to move through all of the screens of data without having to worry where they were.
You could even use the home key to move to the top of the first screen, page up to the top of the previous screen and page down to get to the next screen. Your choice.
Or you could use F8 to popup a menu list of screens and allow the user to select the one wanted.
Richard Kreiss
GCC Consulting
rkreiss at gccconsulting.net
More information about the Filepro-list
mailing list