Thanks Al.

- I will check the private versus Public network tomorrow. I don't know how that would affect the VFP to see the Mapped Drive, but we'll see.
- Yes, I have been using NET USE with persistent: YES.
- I ran NET USE commands via the same USER profile than the App runs (not as admin).

Regards;
Cyrus

>>I have windows 10 station I call server (where VFP data files are located) and a windows 10 station I call station (which shares the data files on server station)..
>>
>>I am having a problem with VFP seeing the S: drive (which is the Server station's D; drive mapped as S: on the station).
>>This was working up to 2 weeks ago for couple years. All of a sudden my VFP application is no longer seeing files across the network on the server.
>>I guess it probably was Windows Update that caused it.
>>
>>It is important to note that The disk dropdowns also no longer list (see) the Mapped Network drives.
>>I have rebooted, disconnected and reconnected the network drives, I have also use NET USE command to establish the Mapped Network drive.
>>Still The Server drives are still not visible on the station.
>>Please note that the S: drive is visible on the Command Prompt.
>>
>>Short of reinstalling windows on the station, or going back to a Restore point prior to a possible Windows Update, I am wondering if anybody else on this forum has encountered this weird situation?
>
>The first thing I'd check would be that your network type is still "Private". If it has been somehow switched to "Public" that could explain what you're seeing, as that mode switches Network Discovery off. You would need to check this on both the "server" and the "workstation".
>
>If at any point while troubleshooting you're asked if you want to enable Network Discovery, answer "Yes" and follow any prompts.
>
>It's worth noting that using NET USE is a quick, power-user way to work around these types of problems. You can add a flag to the end of a NET USE command to make sure it's remembered:
>

>NET USE blah blah /persistent:y
>

>You should also be careful to map drives (either in the shell or via NET USE) using the account that will normally be running your app. If instead you use batch commands that are run as Administrator, either interactively or as scheduled jobs those drive mappings may not appear in the "normal" user profile.