Cancel in CanExit not triggering

[gaby_h]

I have a customer form with a Cancel script in the CanExit event. When I create a new customer directly in customer form, the script is triggered. However when I create a new customer through the lookup pop up window from Invoice form the script is ignored by A5.
I know I can use a field rule for enforcing the rule, but I want the rule to apply only for certain type of invoices (Commercial customer).
The help fiel says that if the Close() has a .f. the canexit will be triggered, I checked the XBasic code in AS and the close() does have the .f. (parentform.close(.f.)).
Please see attache file.

[CALocklin]

Re: Cancel in CanExit not triggering

Personally, I think using the CanExit event is a really bad way to do this but since you insist:

Change the CanExit event to this to solve the immediate problem:

IF parentform:Company.text = ""
   ui_msg_box("Note","Incomplete",UI_INFORMATION_SYMBOL)
   cancel()
END IF

HOWEVER, by just doing that, if someone starts to enter a new record, then they ABSOLUTELY MUST enter a new record or press Ctrl-Alt-Del to shut down the application. There is no way to cancel when, inevitably, somone says "Oops! I didn't really want to do that." (This is the main reason I wouldn't use the CanExit event for this type of thing.)

I have a fix for the problem but please realize that this "fix" will get more and more complicated as you add new fields. Maybe you will never add new fields but may experience says the chances are very good that you will.

To solve the "Oops, I want to cancel this" problem, use this script in the CanExit event:

DIM GLOBAL g_allow_exit as L
IF parentform:Company.text = "" .and. g_allow_exit = .F.
   ui_msg_box("Note","Incomplete",UI_INFORMATION_SYMBOL)
   cancel()
END IF

Then add a "Cancel" button with this code:

parentform.Cancel()
DIM GLOBAL g_allow_exit as L
g_allow_exit = .T.
parentform.Close()

FWIW: This is why I ended up writing almost everything in xbasic. I'm guessing this could be done with action scripting but there were far too many times when either something came up that didn't seem doable in A/S or the A/S only got me 80-90% of what I wanted then the last few percent either had to be "make do", "twisted logic", or "well, it wasn't that important anyway" - or I had to rewrite the whole thing in xbasic. After awhile, I just quite using A/S and now I find it very confusing to work with A/S. With A/S I'm always opening and closing various parts of the A/S and trying to figure out how they work together. With clean xbasic (vs. the mess that A/S has to create in order to work wherever and however it's used), it's all there in one sequential script.

[gaby_h]

Re: Cancel in CanExit not triggering

Thanks Cal for your reply, much appreciated. I used the CanExit because with my limited experience this seemed the easiest way to go about it. With your explanation I see now the problem associated with it. I am starting to realize that AS is not the ideal tool and starting to learn XBasic; it will take me a while before I reach a level where I am able to write in xbasic and do without AS, but I'll get there. Thanks again.

[MikeC]

Re: Cancel in CanExit not triggering

Cal,
I just wanted to agree with you on

it's all there in one sequential script.

This was my number one reason for learning xbasic instead of trying to learn the intricacies of Action Scripts to do what xbasic can do in a much more straight-forward way. It just was getting way too confusing with Action Script and not being able to see what was going on.



Gaby,
I am certain you will not regret your decision.

[gmeredith17]

Re: Cancel in CanExit not triggering

Cal,

Is there a particular reason you have made the g_allow_exit a global variable. Wouldn't a layout variable suffice in this situation. Not criticising just want to know if I have missed something important.

Geoff