Close all open objects

[CDeCinko]

I need exclusive access to a table in order to purge and repopulate it. If a browse or other action is open on that table, my code fails. How can I force all open browses associated with the target table to be closed?

[Stan Mathews]

Re: Close all open objects

Take a look at AlphaSports. The main form offers that option when you close it.

Or in the

AlphaSports Explained

in the webhelp.

If you intended to mean closing down layouts opened by any user on the network, take a look at this on www.learn alpha.com.

[G Gabriel]

Re: Close all open objects

A5_CLOSE_ALL_WINDOWS()
It does what the name implies. You could add that line of code at the start of your script.

And while you are at it, the proper word in alpha is not purge but: zap, or empty a table.

[Bob Arbuthnot]

Re: Close all open objects

Connie,

This is a problem on a network if some workstation has a dialog box on it waiting for a response. To my knowledge there is no way within A5 to force close dialog boxes. Maybe someone will show me the way here...

Bob Arbuthnot

[G Gabriel]

Re: Close all open objects

Bob:

To my knowledge there is no way within A5 to force close dialog boxes. Maybe someone will show me the way here...

You can close modeless boxes, but by definition, not modal ones. That said, and also by definition, it is not possible to have more than one Modal box open at a time nor would you be anywhere else if a modal one is open.

[CALocklin]

Re: Close all open objects

I'm re-opening this in case anyone has a solution:

When I want to shut down an application remotely, I can close any regular form opened 'regularly' - no problem there. However, I cannot close any form opened as "dialog" and I cannot close any xdialog. Anybody know a solution? I'm particularly interested in a solution for xdialogs if possible.

Please don't provide an answer unless you know it will work with Script_schedule():
I can create a script that will close a modeless xdialog and using Script_play() it will close. However, using Script_schedule() will NOT close it and Script_schedule() is required in order to close the app remotely.

[csda1]

Re: Close all open objects

Hi Cal,

I'm re-opening this in case anyone has a solution:

When I want to shut down an application remotely, I can close any regular form opened 'regularly' - no problem there. However, I cannot close any form opened as "dialog" and I cannot close any xdialog. Anybody know a solution? I'm particularly interested in a solution for xdialogs if possible.

Please don't provide an answer unless you know it will work with Script_schedule():
I can create a script that will close a modeless xdialog and using Script_play() it will close. However, using Script_schedule() will NOT close it and Script_schedule() is required in order to close the app remotely.

I haven't checked the script_schedule() function yet, but clearly both the modeless Xdialogs and the forms opened in dialog mode can be closed from an event in a modeless xdialog box (which can be hidden). By setting a timer event in the modeless XDialog and waiting for a scheduled time, it can fire code when needed that can close the forms and modeless XDialogs and other windows. I am not sure if modal xdialog windows can be closed via this method, but probably can be.

You can prove just about any of this by trying to close Alpha 5 using the CSDA Code Utility, and it should exit cleanly (except the issue of modal dialogs). It may be possible to close the modals by executing in the timer event of the modeless dialog box, which might grab temporary control away from the modal dialog box.

[CALocklin]

Re: Close all open objects

I figured that out about an hour after my original post - then decided it was time for dinnner. In fact, issuing a ui_modeless_dlg_close() to close the modal dialog actually does work (tested in v8 and v9) and this is ideal in my situation. The user wants to switch between two dialogs during the normal sequence and using modal dialogs keeps the dialog in 'focus' so the user can just hit the Enter key if everything is normal. If I use modal dialogs, the modal dialog loses focus and the user has to grab the mouse instead.

I still have to test it in the final configuration but I'm pretty sure it will work. Once I've proved it out, I'll post the code.

[csda1]

Re: Close all open objects

Hi Cal,

...In fact, issuing a ui_modeless_dlg_close() to close the modal dialog actually does work (tested in v8 and v9) ...

The above works in all versions 5 and above, probably version 4 too.

...If I use modal dialogs, the modal dialog loses focus and the user has to grab the mouse instead.

I think you meant modeless in the above sentence. In the timer event, or by using an ondeactivate event (check proper name), you could return focus to the modeless dialog box if desired.

[CALocklin]

Re: Close all open objects

I think you meant modeless in the above sentence. In the timer event, or by using an ondeactivate event (check proper name), you could return focus to the modeless dialog box if desired.

Actually, I did mean "modal" but that was just me being stupid. The only reason it "closed" the modal Xdialog is because it was run within the %code% section of the modal xdialog and there was no a_dlg_button = "" after it to keep the dialog open.

I really need to use modal dialogs because modeless dialogs "lose focus" and require the user to grab the mouse to activate the buttons. Most of the time the user can accept the default values and just push the Enter button to accept them. The guys on the line are constantly moving and they'd be upset by anything that took more time. Walking over and pushing the Enter key is much faster than walking over, grabbing the mouse, lining it up with the button, and clicking it. (Some people seem to find that hard to believe but it really is true.)

At any rate, I've spent many hours on this so far and I know there is a solution but putting it all together will take some time. Coordinating a shutdown both with and without xdialogs is part of the problem - sometimes an xdialog will be on screen when a shutdown sequence begins; sometimes it won't. I also discovered that scripts initiated by Script_schedule() don't seem to run as long as a [modal?] xdialog is open. This means I can't initiate the shutdown by having the script change a variable - if the script can't run, it can't change the variable. So, I have to run my checks within the xdialog itself and I have to use a file created by the admin to initiate the workstation close. But, the regular script_schedule() must also run because sometimes the xdialogs won't be open. And, the final shutdown must wait for the xdialogs to close first. Fun, fun, fun.

However, I don't think I can do anymore tonight. It's getting late and my head is starting to throb so I think it's time to give it up until tomorrow.