How can I disable/hide this X (the one by the maximize button)? I need for my users to go thru my closing routines, not just X off the screen.

Unchecking the "System Menu" checkbox in the form's properties will disable the X, but the window can still be closed by Alt-F4.

I my oppinion, a better alternative to disabling the X is attaching your closing logic to the CLOSE event of the form. This event triggers whether X is clicked, Alt-F4 is pressed, or a custom Close button is used.

Dave

[email protected]

http://www.insitechgroup.com

Thanks Dave, I have tried just making the X go to the same logic my save button does, but with limited success. The closing logic (this is a sales invoice) involves a number of further communications with the operator, asking how much the buyer gave, displaying a change amount, asking whether the payment was cash, check, credit card etc.

Further, unchecking the system menu disables the X while I'm in the form designer, but the X is alive again when I execute the window. So I'm maybe doing something in my CREATE event processing which reactivates it, but I don't know what. In the create event I do center the child window on the screen, but no other actions. Just before submitting this, I disabled the centering action and the X is still active on execution, so thats not it.

Glenn,

Is there any help in my reply on the other list?

A general approach for solving a problem with window logic is to think through which processes you need, where you break the processing down into neat, independent parts, and also decide how the parts (processes) should be related. E.g, my suggestion on the other list was to have a process for handling the user-initiated closing of a window. This goes into the CLOSE handler. That might be a problem if you need the CLOSE handler for other stuff, but I don't think you do. I tried to modularize by letting the CLOSE handler do as little as possible - just issue an explanation, and then make sure the window doesn't close. My solution might not suit your case, but at least I would try to keep the separate processes, which in your case might be saving, finalizing user dialog, etc, apart.

- Oystein -

Yes it was helpful. When I came online this morning to check for responses, I came to works and didn't find my inquiry, and forgetting I had posted it to the general discussion I reposted it here. But you got me going down the right path. I still wonder why checking the 'Syetem Menu' off seems to work for most people but not for me, but at this point it is only of academic interest.

Glenn,

I still wonder why checking the 'Syetem Menu' off seems to work for most people but not for me, but at this point it is only of academic interest.

How is this window getting called? If you are using Start_MDIChild I believe it will put the System Menu back. The same might also be true when using Dialog_Box.

[email protected]

SRP Computer Solutions, Inc.

Don, you are right. All of the screens in which I tried to set the X off are invoked with start_mdichild, so thats probably the reason.

View this thread on the Works forum...