...And the workaround is not clear to me:

To work around this problem, place the program and data files on a local volume. If the program has hard-coded drive letters that usually go through mapped network drives, you can create those drives by using the subst command. 

Our app open tables using a path stored in a config table, so the data folder can be where our customer decide. It can be a mapped network disk, a relative path or and UNC path.
If I'm understandig correctly the suggestd workaround, I need to investigate the exact configuration they are using and make them copy the programs and data to a local volume/disk in the Server being accessed by Terminal Services. Am I right?


>You mean mskb #Q294816?
>
>>Thanks Sergey.
>>
>>I found sometbing more directly related with TS by searching the KB using just c0000006.
>>But still the whole thing is a mistery.
>>
>>