@id when starting Windows tied to Tables (AREV Specific)
At 18 OCT 1999 08:01:44PM Claude Mansutti wrote:
Its late at night and I've spent the last hour or two looking for an answer which must be simple, but I just can't see it.
Running Arev 3.12, on Stand Alone
Most of my windows are collectors so I can play with @pseudo etc, but in this rare case, I have created a window tied to a table, With Exclusive locking.
I have an estimate window, and if I enter and accept the next default value on the key prompt (I'm using in house counters and not %SK% etc), I then go to prompt 2 . It asks for a job no. and using Btree.Extract I determine the Record No this job No has in a related table. Say the record No was 20001
If for some reason 20001 fails to meet set criteria the user is prevented from continuing, wc_is% is set to "" etc.
If the user now escapes, and re-enters the window, He/She gets
@id automatically set to 20001, if I escape, it clears it.
What have I done? I've checked and reset @ans, @pseudo, I've run cleardata, clear
More importantly how do I stop this from happening? I'm sure I've overlooked something basic and simple. I hope I've explained the predicament properly.
Thanks in Advance
Claude
At 19 OCT 1999 02:52AM Steve Smith wrote:
I think there is a variable ID_NEW or NEW_ID in Window common which
you set to indicate a new @ID is being entered. Also, OREC may need adjustment in this scenario as well.
Steve
At 19 OCT 1999 11:05AM Claude Mansutti wrote:
Thanks Steve,
I'll Check it out.
By the way, is there a way to capture/debug when the escape key is pressed, i.e. You wish to leave the table.
Claude
At 19 OCT 1999 02:01PM Richard Christensen wrote:
Use the function ESC.TO.EXIT
Declare it first then:
If Esc.to.Exit() then
end else
end
At 19 OCT 1999 03:44PM Victor Engel wrote:
A couple of notes re: esc.to.exit:
It has its own keyboard buffer, so if you have a loop with ESC.TO.EXIT in it, you get a larger type-ahead buffer.
The new READNEXT code includes ESC.TO.EXIT. This logic was added to allow you to escape from long selects. Unfortunately, there are sometimes situations where you want to use ESC.TO.EXIT in a loop that also includes a SELECT. What happens here is that you get to ESC.TO.EXIT commands, one you have control over, the other you don't. In this situation you will have to disable the ESC key before the select or come up with some other alternative.
At 20 OCT 1999 09:35AM Claude Mansutti wrote:
Tried test and capturing New.id and orec at various points, but they were always null. If I capture the pre-prompt of the key field,
@id=20001 or whatever number was returned from the function mentioned at the top of thread.
Long live collector windows!!
Help Please
Claude