How about using the registry to store the next number to use? It's the same idea of the NextID table, but using the registry. Note that this solution will not scale if your application need to be used by multiple users in the future. If this is the case, then you can use a file or a free table.

If you don't really need your record number to be consecutive and space is not a matter, a GUID can be used. It have the advantage of being unique without the need of a depository like the registry or a table.

HTH

>Here is my situation:
>
>I've created Electronic Data Entry piece of Data Entry application. We receive files from registries in some text formats. I created a conversion program for each registry, that creates "source" file. Then another program processes this Source file and creates a work file, called BldMstr. This file has ID field called RecNum.
>
>There are some records in the source file, which should not go to the BldMstr file (nominal sales, for example). However, these records should go to "DoNotProcess" file.
>
>I number records in Source file sequentually.
>
>So, here is a scenario:
>

>BldMstr
>   RecNum - 1
>   RecNum - 2
>   RecNum - 5
>DoNotProcess
>   RecNum - 3
>   RecNum - 4
>
>
>Source File
>   RecNum - 1
>   ...
>   RecNum - 5

>*************************************************************
>In the Electronic Data Entry I allow some manipulations with BldMstr file, which basically allow to add new records. My problem is, I don't know, how to ensure, that each time, I add a record to this BldMstr file, I add a new unique ID.
>
>The DE application is stand-alone (not multiuser), so I was not using additional table (NextID table) idea...
>
>============================================================
>Can you advise something in my situation, please?