I have a VFP8 application that now just hangs on Windows 2000 PCs running the command:

cFileName = GETFILE()

I have created a test .exe that includes this single line and it hangs as well if you have the default folder on the network. The PC completely hangs where you need to do a forced cold boot with the off switch. If you run the test program on the c: drive, then it works fine and even allows you to change drives to the network.

So far no other applications on these PCs seem to have a problem running File/Open such as Office products, Wordpad, Notepad, etc.

This VFP8 application is mostly being used on XP PCs but there are still a handful of Windows 2000 PCs running it. The IT staff maintaining the PCs just finally deployed a bunch of MS Windows patches that included the set released on June 13th that included new restrictions to ActiveX controls. Since the appearance of the problem and the deployment of the patch happened at the same time, it is probably linked. There is also a possibility that changes were made on the server at the same time.

Since the Windows OS of the problem Windows 2000 PCs are not showing SP4, clearly these are not fully patched machines, but it may take a while to get the corporate IT staff to update them. As far as I can tell, the application still runs fine on all XP machines.

I am hopeful that the additional MW Windows 2000 patches to bring them up to SP4 will cure the GETFILE() problem. In the mean time, does anyone have any other suggestions?

Can anyone at least tell me what the Windows .DLL file is called that contains the file common dialog so I can compare versions?

Thanks,
David