Douglas J. Steele said:
Are you saying that the fGetUNCPath function on that page (which uses the
WNetGetConnectionAPI call) doesn't work for you?
Thnaks for the reply. I'm saying that I don't know how to find out if it
works or not. The code assumes a level of understanding I do not have.
Since there is little documentation accompanying it, I cannot discover how
to use it.
I'm sure I've used it successfully in the path. It should be as simple as
fGetUNCPath("E")
For lack of a better idea, I tried ?fGetUNCPath("E") and ?=fGetUNCPath("E")
in the immediate window, but nothing happened except for error messages
saying in one way or the other that more was expected.
Again, I don't know how to make it work. In both code examples the code is
apparently expected to work on a string that represents the drive letter
path, but I have not yet discovered how to plug that string into the
function. The trouble is that there are functions within functions within
functions, with constants and variables interspersed. In Randy's example I
would need to start with the command button's Click event, analyzing the
functions that are used there in an attempt to discover their basis, and
likewise working backward from there. Unfortunately I cannot take the time
that would be needed to sort out all of that. I don't doubt that it is all
quite clear to an experienced developer, but I would have to devote at least
several days I do not have to understanding how to make it work. I probably
need to accept for now that for me this is a problem with no solution.
Unfortunately, I'm at home recuperating from surgery at the moment, so I
can't easily test it.
Get well soon. I appreciate your taking the time to reply.