Back to duplicating a record with child tables.

[preston2]

Re: Back to duplicating a record with child tables.

It sounds like there is a timing issue where the new form is opening before the first form closes. That's why the second form has a number at the end.
The xbasic_wait _for_idle is an attempt to have the first form close before the second form opens.

That said, I always try to avoid explicit code just for this reason

I do not think it is a timing issue but the fact that the original form does not actually close until the script that was run from it finishes and exits. You can put a WAIT_UNTIL() and have it time out for 1 or 2 seconds and it will still open the new form with a number behind its name.

I had started using explicit's in places as I had some issues with non-explicit statements not working well in a multi-user environment. I went ahead and took them out for this right now but I am still highly curious as to why you have to close and reopen the form to get the one to many fields to display the values in the table.

Update:

Changing the code

Parentform.Close(.f.)
xbasic_wait_for_idle()

dim Frm as P
Frm = Form.load("work_orders")
Frm.Index_Set("inv_id")
Frm.find(newinvoice)
Frm.show()
Frm.activate()

this.enable()	'enable button on way out

To:

topparent.fetch_last()
parentform.Repaint()

Seems to work. Need to test more to make sure but it looks like it does the trick.

Using it no longer renames the form as it never closes and the parentform.repaint() populates the one to many fields on the form.

Update to Update:

This turned out to not be reliable. Need to investigate more into it.

[Stan Mathews]

Re: Back to duplicating a record with child tables.

Maybe try it as


codeTxt = <<%code%
dim Frm as P
Frm = Form.load("work_orders")
Frm.Index_Set("inv_id")
Frm.find(newinvoice)
Frm.show()
Frm.activate()
%code%
this.enable() 'enable button on way out
parentform.Close()
on_xbasic_idle(codeTxt,"R")

[preston2]

Re: Back to duplicating a record with child tables.

Sort of works Stan.

I had to comment out the Frm.find(newinvoice) as it would not pick up that variable. I could make it global and then it would.

It totally closes the form, delays a bit and then reopens it.
Problem is it sets some weird query that can only be cleared by clicking a "Show All" button on the form or closing it down and restarting it.

[preston2]

Re: Back to duplicating a record with child tables.

This seems to work.
It does totally close the form and then reopens it after about a second but I may be able to live with that.

I also does not cause the crazy query issue I mentioned above.

codeTxt = <<%code% 
script_play("open_estimates") 'A script I use elsewhere to open the form.
%code% 
parentform.Close() 
on_xbasic_idle(codeTxt,"R")

[pboomwork]

Re: Back to duplicating a record with child tables.

The following can be used to refresh an embedded browse, based on a child records, after additional child records are added outside of the form.

Pwin.Browse_device.resynch()

Where Pwin is a pointer to the window with the form. You can use the Object explorer to get the actual Object Name or use;

topparent:Browse1.resynch()

Where browse1 is the name of the browse that needs to be updated.

Another option for forcing multiple browses to resync is moving to a different parent record and then moving back to the record of interest. Something like.

REcNum = :topparent.recno_goto(xx)

[MoGrace]

Re: Back to duplicating a record with child tables.

The only thing with duplicating a record and then showing it on the existing form is that if the user looks away for a second he's liable to think nothing happened. Why not pop up a form to show the new record in a modified form then allow the user to make a few edits or confirm the record before returning him to the main form?

[preston2]

Re: Back to duplicating a record with child tables.

Robin, I use a ui_msg to tell them they are about to duplicate and then another one that tells them is is done. If they look away, they will be staring at the last message when they look back.

Paul, .resync() does not work on the one to many.

[Ronald Anusiewicz]

Re: Back to duplicating a record with child tables.

Preston,

The problems you are having are directly related to the down side of manipulating data using xbasic and trying to refresh forms using form coding. I hope that makes sense. When you look at my original code, you will see lines that don't appear to be needed. Well, those lines of code were added to make the form behave the way I wanted while using xbasic to change the data. Truthfully, this can be a nightmare. .Refresh(), .resycn() or .repaint() don't always work. That's why I ended up closing the form and reopening the form. When I opened the new form, I had to make sure I navigated to the new entry. That's why I used the form load, etc... Tom Cone and I have talked this over and we both believe it's directly related to timing issues.

I don't know the real answer but the code I provided is working for me in my particular situation.

[preston2]

Re: Back to duplicating a record with child tables.

Ron,

I ended up going with code based on yours but with simplified version of Stan's suggestion for using on_xbasic_idle(codeTxt,"R") instead of the quick re-opening which adds the number after the form name. My form already run topparent.fetch_last() when it starts up and take them to the last record which would be the duplicated one. That is unless two people actually duplicate a record at the same time.

On my form that is all one to one (parent and five children) I used a modified version of your code all the way as it does not matter if it gets reopened with a number after the form name.

But on the form with the one to many, it does matter because they can open other forms and preform a query back to that form. If it has been opened during a duplication with a number after the name and then they query to it from another form, it opens another copy of the form without the number after the name and then you end up with multiple copies of the form opened.

What really get me is this should be simple and part of Alpha's built in functions or methods. But it is like they never realized that most forms are built off a set and when duplicating it would also need to duplicate records from the child tables.

[Ronald Anusiewicz]

Re: Back to duplicating a record with child tables.

Well, it would be nice if duplicating a record would duplicate the children, but it doesn't. I don't know if you allow the deletion of a record, but if you don't use referential Integrity (and it's recommended not to), then you will need to delete each child using xbasic. The code I use is similar to the code I use to add a child.