> >Besides, I don't like writing apps where users go on deleting records > >every once in a while :) > > Hi Dragan - I am doing it this way because it will always be a small > table. > If this table was going to grow, I would use TABLE BUFFERING and there > would > not be any blank or deleted records. what to you think? thanks ..rob Well, I still think that buffering or not, and using a save/revert or not is not the same question. I think we already have another thread where we're talking about that, so let's go there. To make it short on this one, I think that you can use table buffering AND avoid the save/revert button, by simply checking for blank records in the buffer and not issuing TableUpdate() for these records, so they never get written.