>Hi everybody,
>
>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?

I don't see a good reason not to use NextID. It can easily be used in standalone cases too. For Source I'd add another field to other tables keeping SourceID. Otherwise it sounds you need an allocation for source IDs that could be placed 'in the future'.
Cetin