I think it's Server 2008 service Pack 2 Are you saying the program itself should decide where the temp files should be or the config.fpw file?
From: Dave Crozier DaveC@Flexipol.co.uk To: ProFox Email List profox@leafe.com Sent: Wednesday, April 13, 2016 12:06 PM Subject: RE: Program working under on login, not another.
Michael, What server are your TS services running under?
We had untold problems with 2008 hosting TS and since moving to RDS/RDP on 2012 the problems have decreased significantly. The biggest problem with TS is organising where temporary files are created when a single session login is shared over users and we still have this with our VFP apps unless we manually configure where the temp files are to be stored from within VFP.
Dave
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Michael Madigan Sent: 13 April 2016 17:03 To: profox@leafe.com Subject: Program working under on login, not another.
I have a legacy FFW 2.6 program running under terminal services The customer complains that a certain report "hangs" and never completes. I test it on my login, everything is fine. I have them create another login for me using their profile, that works fine. The permissions and setups should all be identical. I have them log into using my login, and it works fine. They have the same default printers. They have the same exact work space and local disk I have no idea what there is left to try.
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
[excessive quoting removed by server]