>Alex
>You have it, Our apps are located on an app server and our data is on a data server. I want the data to stay together includung the ini table but cannot get to the table because the path has not been established. I added a procedure in the main program to load the app object and catch any errors. I may be trying to thin my main to much. I thought there would be a way to keep as much code in the app class as possible. I don't want prg files hanging around that any developer can change. We are trying to use as much generic code as possible using table for data that needs changing so as not to have to recompile the app unless major changes are needed. Does this sound logical?
>Thanks, Chuck
>
>>>If you include that table into the project, the progarm should open it, I believe.
>>
>>Yes, but that would make it read-only, and what would be the gain from just directly hard-coding the path in the EXE? The idea he has, of an INI or a DBF is so the path can be changed at some time - I guess by the user or admin, or at least that's how I read it.

Hi There :)

I think that you are in need of some sort of application launcher
that will read/write localy (on each workstation) path info
(or part of it) and then pass this info to application it launches...
There are some of these launchers available here I think, but
you can also build one to suit your specific situation.

I personaly use free table on each station to store variable part of the path (and some other things) and then real path gets constructed at runtime based on current server position.

Additionaly forms & reports using DE to open tables have to be 'equiped' to change their path settings on the fly, otherwise they might get stucked looking for design time paths 'hardstored' in DE.


Best Regards