A final query about the data-entry topic II just posted. . .

"You¹ll have to make certain your scripts empty this global field when
you change records in the primary table. This is only a few minutes
extra work and makes for a far more professional looking interface."

I'm a little baffled as to how I go about this? It seems to me that
this would involve including a script step that empties the global field
in every possible user action that leaves the current record (for
instance, rather than having a simple button taking you to the next, or
last record, writing a script that does so after clearing the global
field)-- or is there some more general strategy for this?

I'm aspiring to the standard suggested in the Novice Whitepaper that I
eliminate the status area and control use navigation from the database
layout - and I guess this might be an illustration of why that's
desireable, yes?

Albert
(struggling to gain concept along with technique)

Albert wrote:

write a script that clears the globals
call it as a subscript from your navigation scripts. I use 2 navigation
scripts to handle all 'pure' navigation and grr, even in medium to
modestly large solutions. I haven't found the need to routinely clear
all globals except in a couple of situations.


regards

Chris