or, if you want only one executable, you can read from a "config" file  
(bin or INI) wich functions to create on your menu at runtime.
Carlos

Quoting Dimitris Botsis <[EMAIL PROTECTED]>:

> Use compiler directives in your source code so that you can define that
> when compiler directive "A" is active then it's for your first client
> and when you compile with B active then it's for customer B.
> For example :
> {$define customer_a}    //enables customer A
> {$define __customer_b}  // using something like __ to disable customer B
> ...
> ...
> {$ifdef customer_a}
> ...
> ...
> ...
> {$else}
> ...
> ...
> ...
> {$endif}
>
> Check delphi manual for more info.
>
> This way you can have one set of source code and changing only the
> compiler directives (setting active or not), compiles the application
> for every circumstance.
>
> Regards,
> Dimitris Botsis
>
>
> marcus_fen1x wrote:
>> Hi all,
>>
>> I was writting a delphi application for one customer and now I've found
>> another customer with very little change in requirements, now I know i
>> can do it easily, but my question is how come i do it with one single
>> executable like any user before installation can do something and
>> select the version he wants. All i want to do is to avoid double code-
>> base for these two similar applications,there should be something like
>> a config file where user can choice which things he wants from my
>> application and what he doesn't.  how can i do that? any thoughts ?
>>
>> Thanks in anticipation.
>> Marcus
>>
>>
>>
>>
>> Yahoo! Groups Links
>>
>>
>>
>>
>
>


Reply via email to