As others have said, it sounds as if the app must have lots of hard-coded folder references, so perhaps this suggestion is no more (or less) helpful than some of the ones you already have received. However, when I updated a large, old app to work under TS about 3 years ago, I used the API call that returns the Windows temp folder path and then stored that temp folder in an app-level setting to be used everywhere. Admitedly, it was easy in this case because, as old and ugly as most of the code for this app is, the original developer at least used a global variable to hold the temp file folder and then refrenced the folder through that variable everywhere. Or if there were any places where that was not the case, I quickly searched for and replaced them (don't recall now).

The advantage of using the API to get the temp folder path from Windows, at least in Win2K and above, is that, assuming each of the users logs in on unique IDs, Windows will take care of avoiding collisions for you becuase the temp file is under something like \documents and settings\myuserid\local settings\temp.

HTH,
Kelly

>We have a major application and it users the c:\temp directory . We would like a remote office to make use of our app over terminal server. However 1 user conflicts with another when making c:\temp\ tables using our application. It would take us several weeks to find all instances of tables created in C:\temp and recreate these directories in order to user terminal server. Has anyone ever needed to work around this problem before?
>
>Thanks in advance.