Hey Srdjan
The 2 parameters idea is working. We have user script on our server that force maps everyone to the app server and data server. So there are no issues about users mapping differently. \

Thanks for the input

>>Sorry for the late response, been on vacation...
>>That is what we are doing. I didn't mention it before because some people >don't have experience with that.
>>My problem is my supervisor wants to put the app class in a directory with >read execute rights so no one can change it. With the app class on one >server and the ini table with the path settings on another server
>
>Should'nt ini file(s) be at stations instead of another server ?
>
>Because stations themselves will have variations in interpreting
>server path, e.g On one station serverdata could be under mapped G: drive
>on another will be no mapped drive but UNC path etc.
>
>By coupling server locations you are doubling your problems, because now
>on each station you will need to construct two server paths instead of one.
>
>As far as passing two parameters , I think it should not be problem.
>You can put
>
>lparameters par1,par2,..
>local par1,par2,..
>
>as first line in yr app and it should accept any given number of parameters by launcher.
>
>
>Also it seem to me that you have sort of 'political' issues there
>No 'SuperVisor' should interfere at this level in your development.
>Unless of course he has already very precise idea of how things 'have to' be done. In this case 'let him guid you to the light'
>
>Good luck :)