>Hi,
>
>My VFP application works with a Pocket PC (running WM 6.5) via calls to RADI.DLL and Active Sync. It works well in many installation. But with the customer who is using Terminal Server I have the following problem. They installed ActiveSync on their local PC and when the Pocket PC is in the cradle, the user can - through desktop - see all the folders on the Pocket PC. But when they execute a feature of my application that attempts to connect to the Pocket PC they get a message indicating that the VFP application does not "see" the folders. I suppose that the VFP application actually runs on the Terminal Server and there is there is no Pocket PC in a cradle connected. And I don't think it is possible for them to have the Pocket PC at the Terminal Server (not even practical). How would you suggest to resolve this issue?

When a user at workstation WS uses Remote Desktop to connect to a Terminal Server, there is an option to "allow file transfer between host and remote" (or words to that effect). For security reasons, by default, this option is turned off. If the user enables this function, their TS session maps the PC's local drives to the TS session.

If the user starts up Windows Explorer in the terminal services session, they will see mapped network drives such as "C on WS", "D on WS" etc. These do not get assigned drive letters, but are available via their UNCs, which are \\TSCLIENT\C , \\TSCLIENT\D etc.

So, if the Pocket PC folders are available as one or more "drives" in Windows Explorer on WS before connecting to the TS, then they may get mapped as network drives in the TS session. IOW it may "just work".