Hi Paul
If the purpose of the distribution of the unique file is to determin whether it is a single or multiple version. then I would sugest the following way i'm using:
Determin a numeric number based on the name of the client, the date of installation, the type of system (demo / permanent), single or multi user). Have this function in your app as well as in a registration app on your side.

Then let the customer either phone or fax you the his detail and based on that you ca supply him with an acces code. Depending on the the type system you then can rename sertan files copied with the nstallation or recreate them.

I use something similar in my apps but it's structured in my Codemine framework.

Hope this helps.
Willie

Then
>Hi Ken,
>
>Thanks, that is what I was thinking but I was hoping there was an easier way than trying to write code and have to ask the user what drive the disk or cd is in and I would probably have to ask where they loaded the app again in case they changed from the default. Am I on the right track? There isn't an easier way that coding all of this is there?
>
>Thanks again,
>Paul
>
>>Hi Paul,
>>
>>You could create a generic distribution w/o the customer specific file. When creating the individual disks, copy both the generic distribution files as well as the customer specific data file. Then have a post setup executable copy the file over (since setup doesn't know about it), or simply prompt the user to insert the disk on first run.
>>
>>Hope this helps!
>>
>>
>>>The name doesn't need to be unique but the data in the file needs to be unique and needs to be set prior to running the installation. For example, I may need to set a flag as to whether the system purchased is single or multi user. Or, maybe a record that tells how many customers they are allowed to add based upon which version they purchased...
>>>
>>>
>>>>Can you create such table at the very first time apps. runs? You can use user's name as a unique portion of a table name.
>>>>Mark