Calling OUTLOOK (COM) without MS Exchange Server?

[Docpro777]

All VFP-COM objects with MS Outlook seems to require MS Outlook to be installed on every client (assuming if each client wants to publicly share in the COM import/export files from MS Outlook).

VFP calls on the CLIENT's Outlook (and NOT the SERVER's Outlook) with commands like:

oOutLookObject = CreateObject("Outlook.Application&quot
oNameSpace=oOutlookObject.GetNameSpace("MAPI&quot

...etc.

The error message when you attempt to make a COM call on a Server when the client does not have Outlook installed on it is:

"Class definition Outlook.Application not found"

How might one specifically call the Server's Outlook COM objects? Might this problem be solved by:
1) Installing MS Exchange Server?
2) Peculiar VFP Coding that directs calls to a Server's application of Outlook while not affecting the Client's?
3) Keeping Outlook installed on the Server only--Only use this Server to access any Outlook COM objects?

The final goal is synchronization of the Server's VFP-Outlook COM objects into handhelds and/or laptops.

Thanks in advance for ANY suggestions.

Philip M. Traynor, DPM

http://www.doctorprofessional.com

 

[Mike Gagnon]

DocPro777

All VFP-COM objects with MS Outlook seems to require MS Outlook to be installed on every client (assuming if each client wants to publicly share in the COM import/export files from MS Outlook).

CREATEOBJECTEX( ) Function
Creates an instance of a registered COM object (such as a Visual FoxPro Automation server) on a remote computer.


1) Installing MS Exchange Server?

You might be confusing COM Server and MS Exchange server. These are two different things.

2) Peculiar VFP Coding that directs calls to a Server's application of Outlook while not affecting the Client's?

See my suggestion above.





Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.