> This way the user can only add one blank record (by append blank) to the > table. Once a record is added, the next time the user wants to add, the > program uses any blanks or deleted records. I think this is better that > table buffering for this application because it will be one less key stroke > (no SAVE/REVERT). If you do not think so, please tell me why. For quick > adding of one field, in this case, I could do without table buffering. > Table buffering has it's place. Don't get me wrong, I could not live > without TABLE BUFFERING in most cases. thanks...rob > > If I use table buffering, than there > will be another move the user has to make. Wait, wait, this seems to be two different matters. If you use table buffering, you can still check if a record is blank and not submit it to updating. Having the user to click on save/revert is quite another question. From my point of view, the buttons look fine, all the world uses them, and I use them a lot, but where do I use them: in Windows apps like Word, VFP, Netscape etc, which are not data entry forms at all. Imagine a hardline bookkeeper or someone in statistics, having to punch in huge loads of data. Have you ever seen these people? They receive a stack of hand-filled papers, and then use their left hand to go down line by line and roll over to the new paper, and never take the right hand off from the numeric keypad. Now I have to tell them they have to press S or Tab+Tab+Enter or reach for the mouse if they want to save the record, and they have to do it several hundred times a day... no chance. Besides, Enter is quite handy, big, well positioned, as it ever was, to perform the default action. In this case, the default action is by no means "close the form" as it usually is under Windows. Enter has meant "finish data entry in the current field", and it took me quite a lot to customize my classes to prevent the buttons from firing every time I press Enter on some textbox, so now it does have the old meaning in my forms. I may seem oldfashioned, but from my point of view, the one who said "thou shalt not Enter, thou shalt Tab" seems much, much worse. Do they have any good ergonomical reason why should I use Tab after ENTERing a number? Tab is long way left, Enter is just where it should be. In your case, the trick could be done some other way, avoiding the gruesome clicking on save/revert every once in a while, and just not updating the last (empty) record.