I know this topic has come up before, but I don't remember seeing an answer this question:
Has anyone found a way to return to their "Custom Menu" form automatically after a 2nd form has been closed?

That works well... with one exception. I can't seem to make the 2nd form close.

If I place @exit in the code for the command button, it takes me to my custom "Menu" form, but instantly exits that form, bringing me to the Application Menu, and leaving the 2nd form still open as a tab at the bottom.

BTW, placing @exit before @SelectTreeItem like outlined below, causes a crash when run while the custom "Menu" form is NOT open already. (Don't know why it works if "Menu" form is open. It shouldn't matter, should it?)

var success as Int

@exit

success = @SelectTreeItem("Price List!Forms!Search/Update!Price List!MENU")
 

If @exit is placed after @SelectTreeItem, it does not crash, but it functions otherwise (as I would expect in this case) as described above. So it doesn't matter where I place @exit, it always executes after @SelectTreeItem.

When that didn't work, I tried to use @SelectTreeItem rather than @exit to get out of the 2nd form. But both success = @SelectTreeItem("Search Menu!Exit Search Menu") and success = @SelectTreeItem("Add Data Menu!Exit Add Data") do nothing even though they return "1" indicating that they were each successful from their respective modes. And success = @SelectTreeItem("Search Update Menu!Exit Search/Update") only causes Sesame to highlight that selection in blue, it does not execute it. This also returns a "1".

I was able to close the 2nd form from a command button using @macro. But that is not acceptable because popup warnings are deactivated during macro playback, and any changes or updates in the form may be lost because there is no warning, the macro just blindly exits. (That reminds me. @exit is not a good solution anyway, since it exit without saving changes.) I wonder, if @SelectTreeItem functioned properly on the various exit selections, would it give a warning that changes had not yet been saved?

Can you check to see if @SelectTreeItem exits you out of a form? Is it something that I am doing wrong or is this a minor bug?

Thanks.

Carl,

In addition to Mark's comment above, to answer your other questions:

1. @SelectTree Item cannot close the tab you are on. Special provision is made to allow @Exit and macros to close the current form. Programming is tightly bound to a Form, so closing a Form while it is running its programming is very bad. If you do this with a macro, make sure you use @DeferredMacro.

2. Regarding your issue where doing this with a macro won't work because of the confirmation popup, an SBasic method would have the same problem.  On your Close button code, check @Modified yourself. If the Form has unsaved changes, don't call the macro. Or use @SelectTreeItem to save the Form.

3. Regardless of where you call @Exit in your code, it is always deferred until the rest of your code is finished, to avoid closing the Form with programming stil left to run.

I was wondering, is it safe to backup an application while there are open forms displaying data?

I know changes that have not yet been committed on an open form probably won't make it into the backup copy, but other than that, will everthing copy safely?

Quote:


Yes. So long as you are absolutely sure that it is not in active use. That isn't too difficult standalone, but in a client/server environment, it is necessary that everyone take their hands off of their keyboards for a moment. Even with several users, it is unlikely that you will coincide with a write operation. They tend to be very brief. The files are only open when actively being read or written. They are only read during initial loading. Only changes are written, in runtime Sesame during normal operation - so the write operations are very brief.

The next release will also include some features involving the menu tree which you consultant types should like quite a bit.