>Hi:
>
>I'm hearing rumors from our IT staff that someday soon they may no longer allow mapping drives. This is unfortuneate for me because all my applications on the corportate network need to map a drive to get to their data.
>
>To get around this, I'll either have to convert apps to use HTTP (Web) or DCOM. Since the apps are on a private network, DCOM sounds like a good choice. I won't have to setup a web server or have clients connecting through an ISP which subjects them to a lot of network traffic.
>

Why? You can simply use UNCs rather than mapped drives to reference remote resources; if you currently map drive P: to server MyServer and share MyShare, you can use the UNC:

\\MyServer\MyShare

in place of P:

>Using DCOM, one question immediately comes to mind. How do out of process EXE's, which are necessary for DCOM, scale? If I create an out of process EXE and put it on the server, won't it serialize method calls and slow my applications down? How do you handle multiple simultaneous method calls with out of process components when using DCOM? Can you put them in MTS and still use DCOM? Comments\recommendations are appreciated.
>
>Thanx,
>Charlie