Re: XP / VB6 accessing network mapped drives after restart
- From: Chris <no@xxxxxxxx>
- Date: Wed, 10 Aug 2005 21:46:51 -0400
Ian Murrell wrote:
My application writes a text data file to a folder on another computer. The other computer is mapped by drive letter to the root (C) shared folder, eg as G:. The network is simple peer2peer, shared root folders etc.
Immediately after restarting the application computer, and when my application attempts to write to the mapped network computer G:, VB returns a "network not accessible" error.
This error will persist until I open WinExplorer on the local computer and click on the network drive letter G:. I then close Explorer and my application will happily write to the remote folder on G: (until the computer is restarted).
I overcome this in a very awkward manner, writing a script that opens the network drive with the command "explorer \G"
Any assistance greatly appreciated. Ian.
Try using UNC naming convention
\\Server\Share\Filename
Otherwise you may want to post this in a VB6 newsgroup... This is a ..net group.
Chris .
- Follow-Ups:
- Re: XP / VB6 accessing network mapped drives after restart
- From: Ian Murrell
- Re: XP / VB6 accessing network mapped drives after restart
- References:
- XP / VB6 accessing network mapped drives after restart
- From: Ian Murrell
- XP / VB6 accessing network mapped drives after restart
- Prev by Date: Re: Framework 2.0 array redim unsatisfactory performance
- Next by Date: open .NET shell programmatically
- Previous by thread: XP / VB6 accessing network mapped drives after restart
- Next by thread: Re: XP / VB6 accessing network mapped drives after restart
- Index(es):
Relevant Pages
|