parentform.close() problem

[Mike Sabo]

Howdy,

I have run inta a problem using the parentform.close(). I am running 1410-1036 Build. I kept whilling the variables down to:
1. I put a Form into "Record Add" mode. (I do this with a script.)

2. I enter NO data at all.

3. I then execute the parentform.close() in a script. (nothing else. I commented out all other actions in the script.) A5 then:

a. Closes the form
b. Puts up a message box asking whether I want to delete the record.
c. Abends completely.
d. throws 2-3 .mpx files onto the desktop.

Incidentally, the form is not all that complex, but does have a browse embedded into it which is really a reflection of the fields on the form itself. I am pretty sure I can duplicate this at will, if you have a problem reproducing it.

This does not happen with the this.close() method, so I am using that instead.

Also, I am aware of how to get rid of the .mpx files on the desktop, and would rather see them show up, as it is apparently an indicator of problem. (particularly with a byte count of zero, I would suspect)

Thanks,

Mike

[Tom Cone Jr]

RE: parentform.close() problem

Mike,

I think there's a later patch you might want to download and install.

In my own work if I have a script that closes the current form, I include code or action scripting statements at its beginning to check the mode of the form. If it's ENTER or CHANGE I quiz the user whether to cancel or save the pending work. The script then either commits the record or cancels the change. Only when the form is VIEW mode do I proceed on to close out the form. It sounds to me as your sequence may be skipping a few of these steps, so you might try inserting them.

-- tom

[Mike Sabo]

RE: parentform.close() problem

Tom,

Thanks for the reply. I did download the latest and greatest off the site and the problem prevails. You are quite right that the form is not in View mode at the time of close. I was using the .cancel initially, and then exiting. Unfortunately, this leaves a blank record. So, I decided on .delete as my final action before exiting. (I test to see whether 2 of the fields are filled, as I automatically fill the rest in from data collected at the start of the data entry process) I will try getting ito view mode first and then trigger the parentform.close. However, I would contend that it shouldn't matter whether you use this.close or parentform.close. Thankfully it does, as this.close works good, lasts a long time.

Thanks again,

Mike

[whanigsberg]

RE: parentform.close() problem

Mike:

Regarding "this" vs "parentform".

If you have code attached to a button then "this" refers to the button and parentform refers to whatever the button is on which may be the parent form or something else.

"Topparent" refers to the form for sure.

However, if you have a button which plays a script and the script includes the alias "parentform" then what does it refer to? I think it will be unreliable.

With aliases context is everything. If you want to use a script you can get a pointer to the parent form and pass it to the script.

This at least is my experience.

Bill

[Mike Sabo]

RE: parentform.close() problem

Thanks for the thought inducing reply. Perhaps A5 is "thinking" that the parentform is A5 itself? Though, I use the parentform.close() on a form which is solely buttons with no edit capability at all and it just closes the form. That's why I used it again. Fortunately, there are ways around things. I will try using, as per your suggestion, my own alias to forms in the future, as a coding practice.

I also had to back out the 1051 build for the .mpx file problem.That was easier tahn copying the code provided to clean up the files.

I am just starting with A5, so I am appreciative of all the feedback. I gotta say, I got further with A5 in 2 weeks than I did with Access in 2 months. Now THERE is a piece of rubber band code. Once you get one thing coded, 2 others break.

Thanks again!

Mike