>It worked now. So tell me if I got this right. In order to be able to do a delte, the form should be buffered, with set delete and set multilock on. further, when doing a delete, a tableupdate() needs to be issued for the record to be deleted permanently(?) from the table.
>
>On the other hand, if I waere to use the table directly and bind the controls to the fields in the table, a tableupdate is still the way to do a delete.
>
>Am I understanding this correctly? Thanks again.

I'm curious to know...were you doing a tableupdate() after your UPDATE and INSERT statements? I would think so, or else those wouldn't work either.

In order to delete a record, it is not required that you have the table buffered. But SINCE you were buffering the table (with a mode of 5), you had to do a tableupdate() to write the change (a delete, in this case) to disk.

So, binding the controls to the fields is not what really matters here. The issue is the whether the table is buffered or not.

Another option is to use an updateable view, and an updateable view is buffered. You can then bind the view's fields to the controls on your form. When using views, tableupdate() is used to send the changes back to the table.

Do you have either 1000 Things or Effective Techniques from Hentzenwerke? Both books have discussions on buffering and on views that you should find very informative.