order of code execution

[Mike Wilson]

I know I have read something about this a couple of years ago but I can't find it.

I have a 2 table 1:M set. I am trying to copy the parent record into the child table with this code run from a form button. For some reason, the parent record table change executes before the record_data_set() so the record copied to the child table has the updated date. Why is this and what can I do?

 'point to main table
	dim t as P
	t=table.get("main")

' copy current record
	dim vdata as B
	vdata=t.record_data_get()
	
' point to revision table
	dim tt as p
	tt=table.get("revisions")
	tt.enter_begin()
	tt.record_data_set(vdata)
	tt.enter_end(.t.)

' change values in current table
	xbasic_wait_for_idle()

	t.change_begin()
	t.ini_date=date()
	t.change_end(.t.)

'Refresh data in current form at parent level.
	topparent.Resynch()
	topparent.Refresh_Layout()

[Mike Wilson]

Re: order of code execution

I reloaded and patched my a5v10 and it is working as desired. I don't have an explanation for the issue.

[G Gabriel]

Re: order of code execution

For some reason, the parent record table change executes before the record_data_set()so the record copied to the child table has the updated date.

Makes no logical sense whatsoever, not today not tomorrow not ever. I don't know what was going on but you might want to keep kittie away from the computer.

On second thoughts, I think I know what happened and it is not poor Kittie:
You clicked the button twice.
Or maybe Kittie did.
At any rate, I think you need to add one more snippet to the code so that once the parent is updated, it does copy yet again to the child, i.e. Kittie-proof, i.e. if someone clicks the button twice in a row, this wouldn't happen.