>>This seems like a design issue that would be better handled by making the client number a variable (rather than hard coded) that can either be passed to the exe
>
>Each time I get a new order, the client's number is entered as a variable which is then stored in a prg file, which during billing, is called and the number stored in that prg file is then stored in another varibale to process the bills. This means that if the client has another location which means a different number, he/she has to get another licenced copy of the software.
>
>However for clients who operate in outside offices, I plan to give them the ability to bill for services rendered in other plances (client numbers).
>
>Porblem is that this hardcoding goes all over the program and tracing it can be a nightmare. Thats why I am trying to give them separate executables in separate directories. The size of the executable is around 2558KB compressed.
>
>>If there are other differences, can they be handled through configuration rather than duplicating code in multiple places?
>
>Yes, the number of users is also hardcoded, but does not affect billing.
>
>>But in any event, if you need to create desktop icons, the function that I provided should work for you.
>
>I usually, compress using PKZIp and then PKzip installs the folders etc in the startup folders, but does not do desktop shortcuts.

This still seems like a design/licensing issue that would be better resolved with storing the client info in a table or configuration file that is accessed on startup and client number chosen rather than replicating the software all over the place. IMHO, it just seems like more source maintenance than I would want to deal with.