Save problem

[Richard Kreiss]

Ran into in to an interesting problem in one of my clients applications.

After each screen of data is entered, I have an input popup that comes up
asking if all of the data entered is correct before allowing the user to
proceed. If this is the last screen, the routine will execute a <save>.  Any
closing programming that needs to be done is placed at the top of the
processing table.

Since I want to insure that my closing checks are done, I have statements

If: @sn="1" and not finish1
Then: finish1

Now what I found is that F10 <save using keytab-dos> is pressed, the record
is saved, processing goes to the top of the table and since finish1 has not
run, the routine goes to finish1.  However when the processing hits the save
command again, processing just ends at that point and doesn't return to the
top of the table.

Now under most circumstances this is not a problem, but this created a
problem for me as I there are several ending options which wouldn't run when
F10 was pressed.

As there are a fairly large number of fields on the 2 screens involved,
using @sk to capture the Press of F10 was not a good option.  So, I declared
a variable fpsave(1,yesno,g) and added this to

If: @sn="1" and not finish1
Then: fpsave="Y";finish1

Then I added an additional set of programming when 

If:fpsave="Y"
Then: fpsave="";END (or a goto one of the closing sub-routines) 


Richard Kreiss
GCC Consulting
rkreiss at gccconsulting.net