Issue with DriveMapAdd

[JackFlashJI]

I am mapping a drive using the following command:

DriveMapAdd("P:", "\\<servername>\<sharename>", 0, "<username>", "<password>")

The command is running and connecting me to the drive because I have access to data on that drive, but I cannot see the mapped drive.

I right click on my computer and select Map Network Drive, click the drive letter and P is displayed without the mapping.

I open a prompt and enter net use, but it is not displayed

Is there something else I need to add to this very simple script to display the mapped drive?

I am running this on Windows XP.

[PsaltyDS]

I am mapping a drive using the following command:

DriveMapAdd("P:", "\\<servername>\<sharename>", 0, "<username>", "<password>")

The command is running and connecting me to the drive because I have access to data on that drive, but I cannot see the mapped drive.

I right click on my computer and select Map Network Drive, click the drive letter and P is displayed without the mapping.

I open a prompt and enter net use, but it is not displayed

Is there something else I need to add to this very simple script to display the mapped drive?

I am running this on Windows XP.

If you cannot see the mapped drive, then why are you sure "The command is running and connecting me..."?

Do some basic error checking/handling:

If Not DriveMapAdd("P:", "\\<servername>\<sharename>", 0, "<username>", "<password>") Then
      MsgBox(16, "Error", "Drive mapping failed, @error = " & @error)
EndIf

The meaning of the @error codes is in the help file.

[JackFlashJI]

We run an application that uses data from this mapped drive. When the command has been run, we can pull all the data we need. If the command has not been run, then we have to manually map the drive.

So the way that I know the drive has been mapped..... The data is being pulled.

[Legacy99]

Are you mapping just the one drive or are there more? If theres more than one try putting a small pause (like Sleep(500) ) between each mapping. We had a case were there was latency and the mapping would be there but the drive letters would not show up in Windows Explorer. We put the pause in the logon script and have not had the problem for 3 years now (knocks on wood). Microsoft had a long explaination why it happens (timing in writing to some registry keys and the speed of the script running vs the actual mapping) but meh whatever, it worked for us.

[JackFlashJI]

We are only mapping a single drive.