UNC Path exists

[shootsie]

Does anyone know how to determine whether a UNC path exists in VB? I have tried everything and it doesn't work consistantly, even though it may work in debut mode. I have tried:

fso.folderexists("//path/test&quot
dir("//path/test&quot

and it does not work consistently.

Thanks,
Ashley

 

[shootsie]

Also, my permissions are correct to verify.

Thanks.

 

[vb5prgrmr]

Hmmm...

this...
[tt]
fso.folderexists("//path/test&quot
dir("//path/test&quot
[/tt]

needs to be changed to...
[tt]
fso.folderexists("\\path\test&quot
dir("\\path\test&quot
[/tt]

Good Luck

 

[shootsie]

I'm sorry, in the frustration to find the solution I typed it in wrong. I'm actually copying the path directly from explorer.

 

[vb5prgrmr]

Ok, well then you should use something like ...
[tt]
Public Function DoesPathExist(PathToTest As String) As Boolean

If Right(PathToTest, 1) <> &quot;\&quot; Then PathToTest = PathToTest & &quot;\&quot;

If Dir(PathToTest, vbDirectory) <> &quot;&quot; Then DoesPathExist = True

End Function
[/tt]

Good Luck

 

[shootsie]

Sorry, but I tried that too to no avail. I wish I could list everything I tried... it seems as if the app will not wait for the OS to try to connect to the network path. I ended up putting a try-catch block... it seems to work OK although it doesn't really accomplish what I wanted exactly.

 

[rdroske]

I tried the above and got the error &quot;bad file name or number&quot; if the path didn't exist. Don't seem to need trailing slash either, work same with or without.

I'll look for something else but if nothing found I guess you could trap the error and use above...

 

[strongm]

>needs to be changed to...

>fso.folderexists(&quot;\\path\test&quot

Not true; fso attempts to normalise paths, and can hanle all sorts of (horrendous) variants

 

[vb5prgrmr]

>Not true; fso attempts to normalise paths, and can hanle all sorts of (horrendous) variants

Byte why confuse it???

 

[rdroske]

I meant the one from vb5prgrmr (dir())
Yeah must be some other problem fso.fileexists seems to work fine for me too.

If you don't need the Scripting runtime for anything else you can also use the API function PathFileExists

Public Declare Function PathFileExists Lib &quot;shlwapi&quot; _
Alias &quot;PathFileExistsA&quot; _
(ByVal pszPath As String) As Long


tmp = PathFileExists(&quot;\\server\share&quot


Retrurns 1 if exists, 0 if not.

 

[shootsie]

Tried it, I'm afraid. Still nothing. *sigh*

 

[DrJavaJoe]

Is the network cable plugged into the back of the computer

&quot;Two strings walk into a bar. The first string says to the bartender: 'Bartender, I'll have a beer. u.5n$x5t?*&4ru!2[sACC~ErJ'. The second string says: 'Pardon my friend, he isn't NULL terminated'.&quot;

 

[shootsie]

Unfortunately, yes. I have had a *little* headway that might give someone some insight:

I have included a third party control that is a file explorer combo box. It allows me to actually go through explorer, select the folder I want to export to over the network, and then select it. Now when I do:

If (fso.FolderExists(FWComboFileFolder1.Value)) Then
call msgbox &quot;WORKS!&quot;
end if

I get a msgbox. FWComboFileFolder1.Value is equal to the same path (ie, &quot;\\path\test&quot over the network as previously when the user entered it in. EXACTLY. I am sure of this. When the user sets this string value it does not work.

I still need the confirmation of directory to work, however, since later on this app will run without user input. Anything??

 

[rdroske]

Gotta be somg funny about what you are doing when the user enters it cause both fso.folderexists and the API call to PathFileExista definitely work...

Test it with however it will get the path with no user input??

 

[shootsie]

In other words, if I have a constant string or if I pull in the path name from an INI file.

Also, keep in mind that this problem NEVER happens in debug mode. Only when I COMPILE the app.

Ok... I just realized I left an important part out that may or may not have something to do with it. I'm running it as a service. *shrug*

 

[rdroske]

Ahhh, could be a rights issue? I don't have time to test righ now but if you log on as the same account as the service is running under is should behave the same way in debug mode as when compiled and running as a service.

 

[shootsie]

At this point I'm inclined to think it's either that or a network issue. I'll let everyone knwo if I come up with an absolute solution to this. Thanks so much for your help...


...still pluggin' away... -shootsie

 

[shootsie]

For others who find the thread - FYI:

From

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q175948

The service has limited access to network resources, such as shares and pipes, because it has no credentials and must connect using a null session.

 

[rdroske]

Just specify that the service run under a domain account rather that the Local System.

I've written services in VB that access Exchange mailboxes and that is certainly a network resource. Just gave permissions to the mailbox to the same account I had the service running under, could do the same with a share.

I love when I see MS saying it doesn't recommend creating services with VB. I do it with the NTSvc.ocx control I downloaded from their site (and never had a problem).

 

[shootsie]

I'm using that ocx as well. I'm understanding now what the problem is -- but still no finite solution. When I set the service to logon under a user account, it will no longer provide me with my form dialogue.