>>With one of my application, I distribute vfp500.dll and vfp5enu.dll in the directory where the application is installed. On some advantages this was given me, was to allow me to be able to be sure my application will use those files and not any newer files which may be present on the workstation.
>>
>>After several installations, now, I have a report that seems to have a conflict with a Portuguese version of VFP installed. Should I be better to install vfpole5.dll in the application directory as well and not in the Windows system which will assure me that I use vfpole5.dll of the same version as well?
>>
>>Is there any other files which I should put in that directory which can be a conflict with the Portuguese version of VFP which is already installed on the workstation?
>
>In general terms, you want to put any version-sensitive .DLL in the directory that the executable lives in, based on the default search path used by Win32 to locate a .DLL file. The directory containing the executable is searched by default before the shared Windows directory paths. FWIW, the default search order used by the Win32 file system to resolve files (it usesthe SearchPath() API call) is:
>
> (1) The directory where the application executable was loaded
> (2) The current directory
> (3) The Windows system directory (returned by the GetSystemDirectory() API call)
> (4) The Windows directory (returned by the GetWindowsDirectory() API call)
> (5) The directories listed in the PATH environment variable
>
>OLE components are a separate problem; if the IDispatch interface is used, whoever registers last wins, regardless of where the OLE component can be found.

It seems there is another sensitive VFP runtime files I should put in the application directory. The VFP Portuguese version already installed is causing a conflict. Does anyone has any idea of what other VFP runtime files I should put in the application directory so I won't have the VFP Portuguese conflict?