>Finally got it to work.
>
>I spent 4 hours yesterday trying to find something that would work for me before I asked a UT question. I posted my question this morning, I tried your suggestion and it did not work. So I went to the bookstore this morning trying to find some books on Win 32 API. Could not find any books that dealt with netfileenum(). I found one book that discussed wnet*.* but the information was sparse compared to the price. Almost purchased the newest Win 2000 API collection for $ 149.00 but the MSDN lib was on DVD of which I do not have, plus I could not find anything in the indexes of the book on netfileenum(). That made me think...I wonder how much stuff is on my local MSDN install (April 99). A whole lot. After reading the help from MSDN and looking at the code I decided I needed to know what is the return error I was getting, # 5.
>
>I found the documentation for netfileenum() but it did not list the return values for errors just the #Define name. I tried researching that, could not make heads or tails of that information in the MSDN lib.
>
>So I went back out to UT in the KB that you had referred me to. Low and behold I found an article on dealing with API return codes. Cut that code into the program and behold "Access Denied" pops up instead of Error # 5. Changed Servers in my call and behold again, it worked.
>
>Talking about "Diamonds in your own back yard". I never look at the UT FAQ's. Now I am going to get myself very familiar with them.
>
>I am going to write an interface to this routine as a development tool...
>
>Thanks for your suggestions they got me to where I needed to be.

You're welcome. Let me add a couple of comments here.

First, if you're a registered VFP user, you can get a free one year MSDN Library Subscription. Details can be found on the Visual FoxPro home page at Microsoft. It is, however, available on both CD and DVD, and, if you don't have it (and it wasn't free) it would well be worth the price.

Second, if you've got the full Visual Studio, you've got access to more sources. If for example, the MSDN references a constant for the return value of an API call, it also shows the header file. The header files are found in the Include folder beneath the VC98 sub-directory. I just do a search of the .h files in that folder for that constant.

VS also comes with a number of utilities. One, which would be of interest here, would be the Error Lookup utility. You just enter the error number, and it tells you its meaning.

Finally, I'm glad to hear you got everything working.