Dave:

Thanks for the tip. Tried it but problem still remains. Have contacted the local Microsoft and they point out that their MSMAIL32.OCX file is a different date from the one that we are using. The OCX file that we have is size: 92,160 bytes date: 21 June 1995. They will let me know more in due course.

Jon

>check kb article q146219 at the microsoft web site. this looks like it addresses the problem of registring ole controls that are to be used in vfp distributed executables...
>
>>We have developed a VFP application that uses the standard MSMAPI32.OCX OLE control that ships with the VFP Professional edition. We have no problems running our application (.EXE of .APP) on our development machines that have had VFP Professional installed. However, when running the application (.EXE) on a regular Win95 PC, we get OLE errors whenever the MAPI code is reached in our VFP program.
>>
>>We used the VFP SETUP wizard to create the EXE for distribution. We included the MSMAPI32.OCX file in the SETUP wizard and checked that is is an OLE object. It appears that the resulting SETUP program does in some way install the MSMAPI32.OCX OLE control to the destination machine, but it still bombs out. Do we need extra support files to go with the MSMAPI32.OCX file? We have only specified the MSMAPI32.OCX file in the SETUP wizard.
>>
>>The OLE errors that we get vary from machine to machine and also from the type of code being executed in the VFP program. They all point to the fact that the MSMAPI32.OCX OLE control has not been installed properly on the user's machine.
>>
>>Any pointers would be greatly appreciated.
>>
>>Jon Sharp