Jimmy, if you use my "who cares" solution, it will show you the "buffered" PO number. You and users of your app have to understand that that PO number is not "real" until you save the PO. If you abort adding a new PO and then try to add another PO, you'll get yet another (next "virtual" PO number) to show up in your PO textbox.

Look at it this way: even in the real world where you have sequence of pre-numbered invoice numbers on invoices that people create, sometimes you make a mistake on an invoice and discard it and print it on the next invoice. The invoice or PO number is only relevent and important if it's "actual".

>OK, I'll buy into your logic of "who cares if it's not the very next number".
>what would I use in the init event of a text box of the form to show the PO that's being used now?
>
>i.e. : this.value = ?????????????
>
>>This is the default behavior for "TasteTrade-like" way of incremental PK generator. The key field is updated at the time of new record insertion, even if the data is buffered and later aborted. The solution is to:
>>1. Don't worry about the gaps between sequence of auto-incremented numbers. Why does this matter anyway?
>>2. Don't use buffering directly on the table. Use some derivitive of SCATTER method and only update to actual table when saving.
>>
>>HTH
>>
>>>I have an incremental number generator (primary key) that I use for a P.O. number. I'm using Optimistic Buffering. The problem is that when I simply exit without saving and enter again, it increments again. The buffer doesn't clear until I close foxpro. what command can i use in the exit click event that will CLEAR THE BUFFER?