How do I return to a form or menu after doing something in a memory form

[terryd]

I have a memory form with a browse procedure and a start button called transfer
Each record in the browse has a tag Yes/No button.
As I tag each record in the browse  a record is inserted into my tagged table, untagging  will remove the record.
After tagging certain records I then click the transfer button.
In the Onclick tag of the transfer button I call a source procedure TagTransfer which loops through the records in the tagged file and does certain processes. Although I do not have a progress procedure the progress field in this tag has the browse name
The TagTransfer procedure works fine, all the changes are done to the various tables and the tag records are removed as each record is processed. A trace at the end of the processed code shows that the end of the source processing has been reached.
However I am still left in the memory Form with the Transfer button greyed out.
Logging out of the application and logging in again shows that the tagged records in the browse have been processed but I would like to either reset the form on completion to display the amended records or if that is not possible to go back to the menu.
The Transfer button is only undimmed if I log out and then back in again, going to the menu and returning to the form still has the Transfer button greyed out

[attachment deleted by admin]

[terryd]

Bruce I have emailed you the file SamsungReturns810Example.rar directly

[Bruce]

Hi Terry,

In the example you sent me, I'm getting a GPF on the ACCESS:returns.Update()  statement in TagTransfer.
(I haven't followed that, but I expect it's possibly to do with there being no error checking on theFETCH above it, and I'm probably missing data or something.)

But looking at the procedure I can see a probably problem with your setup. Your "Start" button does not have a Progress Bar control. Indeed you've set the button itself as the progress control, and I suspect that won't work well at all.

Basically the progress control would get to 100%, and then refresh the button so it's not disabled. No progress, no refresh.

cheers
Bruce

[terryd]

Thanks Bruce
I did mention that I didn't use a progress bar control. Does this mean I have to use a progress bar control even though the operation take a second or two?

[Bruce]

>> I did mention that I didn't use a progress bar control.

then don't use a "Start" type button.

>> Does this mean I have to use a progress bar control even though the operation take a second or two?

no, set your button type to be "button" - and make the call to your source procedure manually in the regular "server side code" embed point in validate::buttonId routine.

cheers
Bruce

[terryd]

Thanks. I'll give it a whirl