Your choice. Personally, I prefer to do it at the table level (in the form's Load or Init), because that lets you choose between row and table buffering. If you do at the form level, you have to use row buffering (except for grids).
Do I have to turn buffering off to delete a record?
Keep in mind that SELECT works directly on the physical data, not on the buffered data (at least, that's its default behaviour). It is unusual in that respect. Almost all other commands are aware of the buffer. So, if you do a SELECT before you commit the data, it won't see the changes you have made. That might explain why it's not showing the deleted records. Try doing a browse to see if you can see the deletions.
Mike
__________________________________
Mike Lewis (Edinburgh, Scotland)
Remember TABLEUPDATE() without using any parameters works on the currently active workarea.
You don't select PAGES, DELETE FROM PAGES works on the PAGES table/alias, but also does not select it.
It would be better to be verbose about the parameterisation of Tableupdate to let it do what you want. Also you need to consider the case TABLEUPDATE returns .F.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.