Maybe there is a better way but at the moment if I want to replicate ewbsrvr.exe  on a 2nd machine in the network (eg for use as a backup server) then whenever I alter ewbsrvr.ini on the main machine then I also change  ewbsrvr.ini on the backup machine  I have noticed however the path specified for the LocalTempTablesPath does not seem to make any difference to the running of my app  even if it a path that does not exist.  Can i therefere ignore this value and  if so what is its purpose Is it perhaps for apps that employ functions I do not use

Thanks

Michael,

<< Maybe there is a better way but at the moment if I want to replicate ewbsrvr.exe  on a 2nd machine in the network (eg for use as a backup server) then whenever I alter ewbsrvr.ini on the main machine then I also change  ewbsrvr.ini on the backup machine  I have noticed however the path specified for the LocalTempTablesPath does not seem to make any difference to the running of my app  even if it a path that does not exist.  Can i therefere ignore this value and  if so what is its purpose Is it perhaps for apps that employ functions I do not use >>

Are you using a local or remote ElevateDB session for your ElevateDB dataset(s) ?  That setting applies to local ElevateDB sessions only.

Tim Young
Elevate Software
www.elevatesoft.com

Are you using a local or remote ElevateDB session for your ElevateDB dataset(s) ?  That setting applies to local ElevateDB sessions only.


I am running remote so thanks that clears that up for me