I have now fixed this problem:)

It turned out I needed to run the Fox.Reg file that came with Nigels Class.

Does anyone know if I can now take the visual Mapi controls off my forms? I would think now that they are not needed.

Will installshield will run Fox.reg file for me if I distribute it as part of my app.


Thanks




>For 3 days now I have been trying to get my my new application installed on a users machine ready for testing.
>
>Everything works fine on my PC but on the users PC it tells me I do not have a licence for MAPI.
>
>It is a communications utility that uses Nigel Coates MAPI class.
>
>I have run regsvr to register the OCX and I have made sure that I have included the MAPI controls on my form even though Nigels MAPI class does not need them (it calls MAPI programmitically).
>
>I have been told these controls need to be on a form for them to be registered properly.
>
>This posting from Bela looks like it could be the answer but I am a bit confused by it
>
>

>MSMAPI32.ocx is only a 'wrapper' for MAPI. You have to install MAPI before installing MSMAPI32.ocx.
>
>But, once MSMAPI32.ocx is registered ether by regsvr32.exe or programatically, you only get this error,
> if you want to use this ocx by createobject() or addobject().
> These commands requires the client machine to have the design
> time licence. (MS doesnot give you the right to distribute the design time
> licence  to your clients.) How to avoid this?
>Add this control to any of your form at desing time and instantiate that form.
>
>And then use the MAPI control in your program.
>

>
>It says I must install MAPI,is this an option from the Windows NT install disk I must select? Do I have to reinstall the MSMAPI32.OCX afterwards?
>
>How do I ensure all my users machines have this option. I am already using installshield and selecting all the MAPI components there but all the users machines still have this problem. Do I have to do 2 installs, one for MAPI and 1 for my APP?
>
>I had better point out that the executable that is being installed on the users machine never gets run. Instead I am getting him to install the program to his drive C: and then he runs a copy of the exe in his test area on the WAN because it is more convenient for me to give him new executables that way.
>
>My understanding in the past has been that if I give a user an install CD and he runs it then all futher VFP executables will run ok wherever he runs them from since all their componants are available to his machine.
>
>I am now running behind schedule on this project so all help is most gratefully received.