Multithreaded applications and shared library code should use the SetCurrentRtDirectory function with care, or use SetCurrentRtThreadDirectory. The current directory state written by the SetCurrentRtDirectory function is stored as a global variable in each process, therefore multithreaded applications cannot reliably use this value without possible data corruption from other threads that may also be reading or setting this value. This limitation also applies to the GetFullRtPathName function. The exception being when the application is guaranteed to be running in a single thread, for example parsing file names from the command line argument string in the main thread prior to creating any additional threads. Using relative path names in multithreaded applications or shared library code can yield unpredictable results and is not supported.