>What .DLL and what path? I use the Setup Wizard to create the installation disks and have almost 500 users on my system. I have had now only 3 people with this problem.

Unfortunately, the name of the .DLL has everything to do with it, and what's affected is the DECLARE statement for the .DLL. You'll need to track down exactly which DECLARE statement is blowing up, and fix it.

While most of the Win32 API is available across all the Win32 platforms, the .DLL that makes the specific API function available varies from operating system to operating system, and in some cases, from operating system version to operating system version. If you've DECLARED a function as being presented by a specific .DLL, and that .DLL doesn't exist, or doesn't export that function, you'll get the error you've noted previously.

VFP provides a means of avoiding the operating system dependencies with many of the common APIs. Rather than naming a specific .DLL, VFP provides the WIN32API reference, which resolves the .DLL references for the most common API calls through a whole host of possible .DLLs. The palce where this has saved my bacon more than once is in the WNet family of API calls, since Win95/98 and WinNT use different .DLLs to export these functions - if the API DECLARES are done with the IN WIN32API reference, the DECLARE works under both operating systems, where if instead I reference, say MPR.DLL, it only works in one of the two environments.

You also may be encountering a situation where the provider is not present in all cases. i ran into that recently with a reference to "Shell.Application", which i discovered was not present on original Win95 systems that had not had either Office or IE 3.0 or later installed on it. If this is the case, you'll need to check for the existence of the provider and drop/register the provider if it isn't already there.