Oops! I've commented on that elsewhere in the tread. I appologise for my misunderstanding. I think my wetware has hardwired the word 'dirty' with the word 'buffer' ;-)

>Hiya Ken ---
>
>I was referring to dirty data not dirty buffer. Dirty data means typos, accidental keypresses, field deletions....et al.
>
>>
>>It seems to me that this is not directly related to a Save Button, but rather a programming oversight. If at some point you have a dirty buffer, even with a save button, it is because the app hasn't checked for it.
>>
>>>In applications where I have tried to be "bleeding-edge" and not had dedicated save functions, inevitably "dirty" data gets into the tables. Typos, accidental saves, et al. In a perfect world with perfect users....maybe.