Conditional object crashes A5

[Bill Warner]

Here's a peculiar situation:

I have a form with an embedded browse. The form uses a custom toolbar, one button of which closes the form (parentform.close()). I also have a conditional object on the form.

If I set one of the conditions to be equal to a global variable, and go into the browse, and then click on the EXIT button, it crashes. If I open the form and DON'T go into the browse, it's OK. Also, if I set one of the conditions to be equal to a field value, it won't crash from the browse.

Something that also happens, that might relate:

I have an ONKEY script that closes the form when ESC is pressed. This will also crash the program as described above.

It seems the program doesn't like the combination of evaluating a conditional object to a variable AND closing from the browse using ONKEY or the toolbar button.

Any ideas?? All help greatly appreciated.

[Tom Cone Jr]

RE: Conditional object crashes A5

Bill,

Try moving the Exit button off the custom toolbar and place it directly on the form. Does that solve the problem?

-- tom

[JohnZaleski]

RE: Conditional object crashes A5

Bill,
No answer here but a workaround might be to put an object.activate() ( outside the browse ) just before the parentform.close.
John

[whanigsberg]

RE: Conditional object crashes A5

Hi Bill,

What is the exact code of the exit button? In particular does it employ the "parentform" alias (or any other)?

Bill

[Bill Warner]

RE: Conditional object crashes A5

Thanks for the replies.

Tom, a button on the form works fine. I suspect that is because clicking on the button returns focus to the form just before exiting.

John, I tried

parentform.activate()

and

:check_register.activate()

just before parentform.close(). It still crashes.

Bill, the code on the button (and in the ONKEY script) is:

parentform.close()

It's odd to me that this works fine if there is no conditional object (which would tend to argue against an alias problem), or if the cond object does NOT use a variable.

[JohnZaleski]

RE: Conditional object crashes A5

Bill,
How about a button.push() that has the parentform.close() as the code.
John

[whanigsberg]

RE: Conditional object crashes A5

Bill,

I would try
this.close()'on the toolbar
in place of
parentform.close()
because the toolbar has the same context as the form to which it is attached and parentform technically doesn't exist.

Don't ask me how this issue might interact with the presence of a conditional object. That is far to inside for me.

Bill

[Tom Cone Jr]

RE: Conditional object crashes A5

Bill W,

Since the script works on the form but not in the custom toolbar I think maybe Alpha Five is confused about what the term 'parentform' refers to, when run from the toolbar. Is the toolbar part of the form? Is it a separate object altogether? I would think an absolute reference using the actual form name would work better.

--tom

[JohnZaleski]

RE: Conditional object crashes A5

Since it's not confused if the conditional object doesn't have a variable reference and it also crashes in the onkey event, but a button on a form works okay, I still think that a button.activate() and a button.push() in the toolbar code has a pretty decent chance of working.
John

[Bill Warner]

RE: Conditional object crashes A5

Bill, I tried

this.close()

I also tried (per Tom's suggestion)

:check_register.close()

but no difference...it still crashes.

I think I'll end up with replacing the conditional object with another way to do what I want.

Thanks to all of you for your suggestions.

[Bill Warner]

RE: Conditional object crashes A5

John, that sounded like a GREAT idea. Unfortunately, it didn't work.

I also tried

sys_send_keys("{f6}")
parentform.close()

thinking that it would take me out of the browse before closing (since if I manually click on the form before clicking the button, it works).

No go.

[JohnZaleski]

RE: Conditional object crashes A5

Bill,
Just curious here.
1)On the toolbar code, if you just have a button.activate()with nothing else, does it activate the button and not crash???
2)If so, you might try putting nothing else in the toolbar code ( especially a parentform.close ) and put a parentform.close() on the onarrive event of the button.

John

[Tom Cone Jr]

RE: Conditional object crashes A5

Bill W,

Have you verified that the script will close the form when the conditional object is not present in the layout. If my guess is right your script will fail even when the conditional object is omitted altogether, provided it's run from the toolbar, instead of from a button on the form. I continue to think that the toolbar has a different idea about what the 'parentform' is, than do objects on the form itself.

-- tom

[JerryBrightbill]

RE: Conditional object crashes A5

Tom,

I use parentform references frequently from both menus and toolbars without a problem. Normally, I might use a direct reference to a form name, but a number of toolbars and menus are used on more than one form. The only area I have found problems using parentform is from a form opened as a dialog. In that case, Alpha does get confused on exactly how to use the reference parentform.

Jerry

[whanigsberg]

RE: Conditional object crashes A5

Jerry,

I use the "this" alias in toolbar code when I need to refer to the form to which the toolbar is attached.

Bill