My application is being used under Terminal Services (TS) on a Win2000 server. It reads some initial settings from an .ini file, which resides in the \WINDOWS or \WINNT directory (depending on the OS). However, in some circumstances, users logiing in from one area need different settings in the .ini file whereas other users may need another set.
Talking to the tech guy who administers the servers at the client's office, it appears that when the ini file is placed on the server's windows path, the program runs ok, until the second set of different users wants to use it, and then they would overwrite the original settings.
It appears as though if the ini file is placed into the windows directory for the profile settings of the logged in user, the program, using a GetPrivateProfileString API call, looks towards the server's windows directory rather than the logged in user's profile windows directory.
Is there something we have missed? I want to be able to provide a different ini file for each user.
Any help is greatfully appreciated.