>If my development computer can see the network neighbohood why can't the VB drive control?
Well, drive control uses drives related Windows API (ie physical peripherals) whereas network neighborhood uses the Network API (from Novell and NT services for example, or any network).
Drives related Windows API doesn't support UNC names since it's designed in reference to old Win16 standalone machine functions, wher each resource is known physically, ie A:, C:, D:,...
If you want to see Network resources you'll have to use the API that fit your needs instead of the drive control OCX.
Here you'll find a goo example of using the API :
http://members.aol.com/btmtz/vb/browsdlg/index.htmHTH
