Erik,

Rebooting was the first thing that I tried including turning off all other running programs. It seems to be a problem with Windows finding the shell32.dll file. If I copy the d:\winnt\system32\shell32.dll file to the directory that I am running my VFP code from, then it works fine. That's strange that a file in the windows system directory can't be found. And the fact that it works if I copy the file over would indicate that the files are OK and not corrupted.

In looking in the Registry I see all references to shell32.dll that have a path have it as d:\winnt\system32\shell32.dll (or %System Root%\system32\).

The only things that strange (but I have no idea) is that in HKEY_LOCAL_MACHINE\Software\Classes\Applications\Shell32.dll the data shows "value not set". Also in HKEY_LOCAL_MACHINE\Software\Classes\Visual FoxPro.Application.6 under Shell\Open\Command it lists VFP6.exe. Maybe that's right but I don't know. The title bar in the error dialog box did say "VFP6.exe - Entry Point Not Found" so maybe this should not be VFP6.exe but Shell32.dll. My windows 98 machine does not have this catagory.

If this is something messed up in the registry, do you have any ideas of what can be re-installed that might fix the problem? Do you have a Win 2000 machine that you could check your registry settings to see if they match the two above?

Any help would be appreciated.

Ed

>>I've run into this ShellExecute problem in Windows 2000 and wonder if anybody else has seen this or not. I'm using VFP 6.0 SP4, Windows 2000 Server, Office SP1.
>>
>>If I run this code:
>>
>>DECLARE Integer ShellExecute IN Shell32.dll LONG, STRING, STRING, STRING, STRING, LONG
>>
>>?ShellExecute(0,"Open","mailto:ehardin@hardin-soft.com?subject=test","","",1)
>>
>>I get the error: Title = "VFP6 - Entry Point Not Found" and Message = "The procedure entry point UninitializeCriticalSection could not be located in the dynamic link library KERNAL32.dll" The error occures when running the ?ShellExecute(... line.
>
>I hjave never seen this, and I have ShellExecute calls running on machines with all Win OSs. Has the machine been rebooted recently? This sounds like a broken dll...