Re: VB6/XP mapped drive connection problem
- From: "Ian Murrell" <IanMurrell@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 11 Aug 2005 16:05:03 -0700
Thanks Ted.
I was hopefull there might have been another way!
All the best,
Ian.
"Ted" wrote:
>
> In the Windows Explorer, click Tools\Map Network Drive
> select the mapped drive and select the "Reconnect At Logon" option.
>
> It is better if you use UNC path than using MAPPED drive.
> \\Computername\ShareName or drive letter
>
>
>
>
> "Ian Murrell" <IanMurrell@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:03B3FBB4-9D15-404D-856D-C4CBA46B70BD@xxxxxxxxxxxxxxxx
> > 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.
> >
> >
>
>
>
.
- References:
- VB6/XP mapped drive connection problem
- From: Ian Murrell
- VB6/XP mapped drive connection problem
- Prev by Date: Re: OT (Sorta): DLL Registration under Restricted User Mode
- Next by Date: Re: OT (Sorta): DLL Registration under Restricted User Mode
- Previous by thread: VB6/XP mapped drive connection problem
- Next by thread: display only one record in crystal report using VB
- Index(es):
Relevant Pages
|
