Run command affected by data file storage location

[Ken Buckley]

I launch another program from within Lookout using the "Run" command. This program reads a config file from the same directory that the executable file is in. When I changed the location that Lookout data files are stored from the install default of c:\Lookout to a remote drive the program I am trying to launch gave the error that it could not find its configuration file. The path to the executable is specified in the "Run" command. Moving the config file to the new data file location does not help. It is behaving as though the instance of the executable is now in a different directory but I don't know which directory or how to find it. Any help appreciated.

Ken

[Khalid]

Hello Ken,

Are you passing the config file as a parameter to the executable in the Run Object?  Can you provide the command you have in the Run object? 

Thanks,

-Khalid

[Ken Buckley]

Hi Khalid,
    I am not passing the config file as a parameter. I hardcoded the name of the config file in the program (being lazy) without a directory path assuming that if the executable and the config file are in the same directory everything will be ok. The Run command is "c:\OPC Processes\GasPhaseCH3I.exe" (with the quotation marks). The config file is also in c:\OPC Processes. When the Options>System>Data files location = c:\lookout the program finds its config file. When I change the 'Data files location' to a network drive (m:\life science\DataFiles) the program does not find its config file.

Ken

[Khalid]

Hi Ken,

I am guessing explicitly specifying the full path of the config file in your executable works, right?  At least you have this as a workaround. 

What version of Lookout are you using?  Because I don't have that option for default data -- the option I have (in Lookout 6.0) is for the Citadel database path.  In any case, I am not sure how changing Lookout's data folder would affect the executable's ability to find the config file. 

What kind of an app is this executable?  Apparently it is, or rather, was able to find the config file with a relative path.  But changing the Lookout's data destination seems to have upset this relative path. 

Sorry for not being of much help.

-Khalid