BWETTLAUFER wrote on Apr 16^th, 2014 at 1:00pm:


Next file? Are you saying that it goes on to the next record?

In any case, you could have the mass update check the time of day, or a flag in a file, and not do anything other than advance records, if it is too late or the flag is set.

BWETTLAUFER wrote on Apr 16^th, 2014 at 9:57pm:


Do you mean the next record or do you have multiple files it is processing?

Quote:


Checking a keystroke is difficult for exactly the same reason it is difficult to interrupt a mass update using CTRL-SHIFT-End.

GUI programs, like Sesame client are either waiting on the "event loop" or are processing based on the last event. A mass update is a lot of processing in response to an event. It can check with the event loop to see if any events need to be dealt with, but doing so opens up the possibility that the user will make menu selections or keystrokes that will distract Sesame, rather than dedicatedly running the mass update. So we set a bunch of flags telling the Sesame window to ignore most events while the MU is running, and only check the event loop for the magic keystroke once per each top level record. A sudden interruption to a MU is usually a bad mistake, in that it may leave a record half modified.

If Sesame gets that keystroke, it should stop advancing the top level record soon afterward and interrupt the MU. But, even if that works, it may be better to let the MU run to completion, but simply skip doing anything more to the subsequent records. This can be done by checking if a file contains a flag, or exists at all, and then bracing the "main" program with a conditional. You could attempt to read the keyboard using @GetFromKeyboard and then forcing the current record to the last record to end the MU, or setting a global flag and doing nothing more to each record and letting Sesame advance to the end of the set.

BWETTLAUFER wrote on Apr 17^th, 2014 at 2:21pm:


The only sticking point I see with that plan are jumping to the last record and being able to check if the file exists fast enough.

It may be better to make all of the programming in the MU conditional on the file not existing, rather than trying to force the current record. That way, there is little chance that the MU would reset the current record (I'm not sure if it will).

Can you think of any reason why CTRL-SHIFT-End is not working for you in your case? I just tried it here with a simple MU and it stopped quite happily.

Okay, I think I have my solution ... with one small issue.

When I run my mass update, in GLOBAL code it creates the following text file on the client machine:

if gProceed = "YES"
{
	vFileHandle = fileOpen("C:\Sesame2\keepgoing.txt")
	FileWrite("C:\Sesame2\keepgoing.txt",@serverdate())
	FileClose("C:\Sesame2\keepgoing.txt")
}
 

And as it runs each item in the mass update, in not-GLOBAL code, it checks for the text file, jumping to the end if the file disappears:

if not FileExists("C:\Sesame2\keepgoing.txt")
{
	FormResultSetCurrentPosition("DR Screen", @resultsettotal())

}
 

However, my delete function doesn't work because it says the text file is in use by Sesame -- even though I used the FileClose command.  Why is that?

Also, did you try using @EventState? It looks like it may be a simpler solution.

I am still confused why the CTRL-SHIFT-End combo does not work for you.