I don't think that separating data from an application means that you can't have tables under your application directory that store information that is specific to each installation, such as user preferences.

>Thanks Sergey
>
>This is one of the approaches I have considered.
>
>However using the Windows registery means that each workstation has to be revisited in the event of a change of location for our data.
>
>And storing it in an INI file with the application means we have not achieved 100% seperation.
>
>I guess I will end up having to use an INI file since there seems to be absolutely no other way of doing it.
>
>
>
>>>Our department has finally decided on an approach of keeping all data completely separate from the applications.
>>>
>>>This will enforce the discipline on us required for any possible upsizing that may be required later.
>>>
>>>This is fine...except if I cannot store any data of any kind with the application how do I tell my application where the database container for the application is located.
>>>
>>>At the bare minimum I must store at least one path.
>>>
>>>Or I must hardcode at least one path into my application. This of course goes against the grain of what I have practised for years.
>>>
>>>I can think of a few options none of them very tidy.
>>>
>>>How do other people deal with this situation?
>>

---

>>You don't have to harcode path into your application but you have to store it outside of your application.
>>You can use Windows Registry, INI file or table to store it.