xbasic delete code running before delete

[Ronald Anusiewicz]

See attached database. Open the form. I tried to describe the problem in the text box.

The OnPush script runs completely before the delete takes place. I want the delete to finish first and then have the code after the delete function execute.

Thanks

Ron

[Tom Cone Jr]

Re: xbasic delete code running before delete

Ron, this is another case where I'm glad I never mix form level code with table level code when writing changes to a table. I've modified the script to work entirely with table level code and I think it gives you the desired result.

dim tbl as p
dim vrecord as n
tbl = table.current(2)
vrecord = tbl.recno()

ui_msg_box("Deleting","You are going to delete record number " + vrecord)
'topparent:Browse1.delete_record()  [COLOR="Red"]<---- form level code, manipulates table through the GUI[/COLOR]
tbl.change_begin()   ' [COLOR="red"]<------ table level code begins here, manipulates table directly[/COLOR]
tbl.delete()
tbl.change_end(.t.)

parentform:browse1.refresh()
ui_msg_box("Note","The selected Item has been deleted")
vrecord = tbl.recno()
ui_msg_box("Current Record","The current record is " + vrecord)

[Ronald Anusiewicz]

Re: xbasic delete code running before delete

Hi Tom,

Thank you for your reply.

I understand what you are saying , but to a certain extent, you have to mix the levels of code. Otherwise the form won't refresh an show the changes. Incorporating your recommendation and making some other changes, this code does appear to do what I want.

Should this be done differently?

dim tbl as p
dim vrecord as n
tbl = table.current(2)
vrecord = tbl.recno()

ui_msg_box("Deleting","You are going to delete record number " + vrecord)
tbl.change_begin()   ' <------ table level code begins here, manipulates table directly
tbl.delete()
tbl.change_end(.t.)

ui_msg_box("Note","The selected Item has been deleted")
parentform:browse1.activate()
parentform:browse1.resynch()

ui_yield()
vrecord = tbl.recno()
topparent:Browse_recno.refresh()
ui_msg_box("Current Record","The current record is " + vrecord)

[MikeC]

Re: xbasic delete code running before delete

I think the simplist way when timing issues occur (or to prevent them from the getgo) is to use a function instead. Take your script for delete and insert it into a function...place the function where it needs to be. If still an issue do the same for any prior script. Only takes a minute or less to do this.

[Tom Cone Jr]

Re: xbasic delete code running before delete

Mike, that's a very good point. Perhaps you'll build an example for us here (using the "parentform:browse_object.delete_record()" method for deleting the record through the GUI). I started to do it that way myself, but the problem of passing form and object names as parameters to the function caused me to look in simpler directions.

[Ronald Anusiewicz]

Re: xbasic delete code running before delete

Hi Mike,

When I started to run into this problem, my first methodology was to use a UDF. As I understand it, all execution of code stops until the UDF finishes executing.

Well, no matter what I tried, I couldn't get it to work the way I wanted. Even though the line:

topparent:Browse1.delete_record()

was embedded in the function, the delete did not occur until after the script finished running.:(

That's when I developed the test database and posted this example.:)

[MikeC]

Re: xbasic delete code running before delete

Tom, Ronald,

Apparently I use table methods almost entirely, especially for record deletion (or an operation). There are those Alpha made functions like the browse.delete_record() which give an Alpha message no matter what is done...and you are correct in that it seems to override all other functions and makes all else subordinate. Too bad Alpha doesn't go through their functions like this and make their messages optional (wishlist).

My premise of using UDF to prevent timing issues is valid but obviously does not always work when particular Alpha functions are used. :(