BorlandTalk.com Borland discussion newsgroups   Archives   FAQ   Search   Memberlist   Usergroups   Register   Profile   Log in to check your private messages   Log in  Incorrect Function - MSOutlook 2003          BorlandTalk.com Forum Index -> Delphi OLE Automation View previous topic :: View next topic   Author Message Peter Batten Guest Posted: Thu Jul 06, 2006 3:42 am    Post subject: Incorrect Function - MSOutlook 2003 I have a number of MSOutlook functions working perfectly on most systems. I now have 2 user reports of an "Incorrect Function" error when connecting to Outlook using operating system WinXP and Outlook 2003. I am guessing that this is a subtle syntax error in the different versions. I am unable to duplicate the error and not all machines with the same configuration report the same error. Any clues appreciated TIA Peter Back to top Dmitry Streblechenko Guest Posted: Thu Jul 06, 2006 10:07 pm    Post subject: Re: Incorrect Function - MSOutlook 2003 Which lines of code exactly cause those errors? The latest SPs of Outlook tend to return non-critical (>0) errors from several methods (most notably MailItem.Display). Such errors can be safely ignored, but Delphi gets all freaked out because it only tests for S_OK (=0) instead of SUCCEEDED (>0). Dmitry Streblechenko (MVP) http://www.dimastr.com/ OutlookSpy - Outlook, CDO and MAPI Developer Tool "Peter Batten" <datafast (AT) tpgi (DOT) com.au> wrote in message news:44ac4063$1 (AT) newsgroups (DOT) borland.com... Quote: I have a number of MSOutlook functions working perfectly on most systems. I now have 2 user reports of an "Incorrect Function" error when connecting to Outlook using operating system WinXP and Outlook 2003. I am guessing that this is a subtle syntax error in the different versions. I am unable to duplicate the error and not all machines with the same configuration report the same error. Any clues appreciated TIA Peter Back to top Peter Batten Guest Posted: Sat Jul 08, 2006 4:30 am    Post subject: Re: Incorrect Function - MSOutlook 2003 So Dmitry, Are you suggesting that placing an error handler around the display method should resolve this? I am not quite sure I understand the difference between S_OK and SUCCEEDED as I don't see a return value for Display "Dmitry Streblechenko" <dmitry (AT) dimastr (DOT) com> wrote in message news:44ad4298$1 (AT) newsgroups (DOT) borland.com... Quote: Which lines of code exactly cause those errors? The latest SPs of Outlook tend to return non-critical (>0) errors from several methods (most notably MailItem.Display). Such errors can be safely ignored, but Delphi gets all freaked out because it only tests for S_OK (=0) instead of SUCCEEDED (>0). Dmitry Streblechenko (MVP) http://www.dimastr.com/ OutlookSpy - Outlook, CDO and MAPI Developer Tool "Peter Batten" <datafast (AT) tpgi (DOT) com.au> wrote in message news:44ac4063$1 (AT) newsgroups (DOT) borland.com... I have a number of MSOutlook functions working perfectly on most systems. I now have 2 user reports of an "Incorrect Function" error when connecting to Outlook using operating system WinXP and Outlook 2003. I am guessing that this is a subtle syntax error in the different versions. I am unable to duplicate the error and not all machines with the same configuration report the same error. Any clues appreciated TIA Peter Back to top Dmitry Streblechenko Guest Posted: Sat Jul 08, 2006 11:18 pm    Post subject: Re: Incorrect Function - MSOutlook 2003 Yes, a try...except block would do. All COM automation methods return an integer result code (HRESULT), it is just Delphi (and VB) hides that by making what is known in Delphi as safecall calling convention: on the low level, a function is called, the last [out] parameter is treated as the function result, and the compiler checks the real function return result. Delphi raises an error it is anything but S_OK (0), but VB checks if it is > 0 (that's what SUCCEEDED macro/function does). You can turn off safecall mapping before importing a type library ("Tool | Environment Optiond | Typer Library | SafeCall Funcction Mapping"), then import the Outlook type library - all method will return HResult with an extra [out] parameter. Dmitry Streblechenko (MVP) http://www.dimastr.com/ OutlookSpy - Outlook, CDO and MAPI Developer Tool "Peter Batten" <datafast (AT) tpgi (DOT) com.au> wrote in message news:44aeeed6 (AT) newsgroups (DOT) borland.com... Quote: So Dmitry, Are you suggesting that placing an error handler around the display method should resolve this? I am not quite sure I understand the difference between S_OK and SUCCEEDED as I don't see a return value for Display "Dmitry Streblechenko" <dmitry (AT) dimastr (DOT) com> wrote in message news:44ad4298$1 (AT) newsgroups (DOT) borland.com... Which lines of code exactly cause those errors? The latest SPs of Outlook tend to return non-critical (>0) errors from several methods (most notably MailItem.Display). Such errors can be safely ignored, but Delphi gets all freaked out because it only tests for S_OK (=0) instead of SUCCEEDED (>0). Dmitry Streblechenko (MVP) http://www.dimastr.com/ OutlookSpy - Outlook, CDO and MAPI Developer Tool "Peter Batten" <datafast (AT) tpgi (DOT) com.au> wrote in message news:44ac4063$1 (AT) newsgroups (DOT) borland.com... I have a number of MSOutlook functions working perfectly on most systems. I now have 2 user reports of an "Incorrect Function" error when connecting to Outlook using operating system WinXP and Outlook 2003. I am guessing that this is a subtle syntax error in the different versions. I am unable to duplicate the error and not all machines with the same configuration report the same error. Any clues appreciated TIA Peter Back to top Peter Batten Guest Posted: Sun Jul 09, 2006 3:52 am    Post subject: Re: Incorrect Function - MSOutlook 2003 Thanks Dmitry, I wish this knowledge was better published in the Delphi Help. Anyway, the exception handler has been incorporated so I will get the users experiencing the problem to test it and see how we go. Regards Peter "Dmitry Streblechenko" <dmitry (AT) dimastr (DOT) com> wrote in message news:44aff65b$1 (AT) newsgroups (DOT) borland.com... Quote: Yes, a try...except block would do. All COM automation methods return an integer result code (HRESULT), it is just Delphi (and VB) hides that by making what is known in Delphi as safecall calling convention: on the low level, a function is called, the last [out] parameter is treated as the function result, and the compiler checks the real function return result. Delphi raises an error it is anything but S_OK (0), but VB checks if it is > 0 (that's what SUCCEEDED macro/function does). You can turn off safecall mapping before importing a type library ("Tool | Environment Optiond | Typer Library | SafeCall Funcction Mapping"), then import the Outlook type library - all method will return HResult with an extra [out] parameter. Dmitry Streblechenko (MVP) http://www.dimastr.com/ OutlookSpy - Outlook, CDO and MAPI Developer Tool "Peter Batten" <datafast (AT) tpgi (DOT) com.au> wrote in message news:44aeeed6 (AT) newsgroups (DOT) borland.com... So Dmitry, Are you suggesting that placing an error handler around the display method should resolve this? I am not quite sure I understand the difference between S_OK and SUCCEEDED as I don't see a return value for Display "Dmitry Streblechenko" <dmitry (AT) dimastr (DOT) com> wrote in message news:44ad4298$1 (AT) newsgroups (DOT) borland.com... Which lines of code exactly cause those errors? The latest SPs of Outlook tend to return non-critical (>0) errors from several methods (most notably MailItem.Display). Such errors can be safely ignored, but Delphi gets all freaked out because it only tests for S_OK (=0) instead of SUCCEEDED (>0). Dmitry Streblechenko (MVP) http://www.dimastr.com/ OutlookSpy - Outlook, CDO and MAPI Developer Tool "Peter Batten" <datafast (AT) tpgi (DOT) com.au> wrote in message news:44ac4063$1 (AT) newsgroups (DOT) borland.com... I have a number of MSOutlook functions working perfectly on most systems. I now have 2 user reports of an "Incorrect Function" error when connecting to Outlook using operating system WinXP and Outlook 2003. I am guessing that this is a subtle syntax error in the different versions. I am unable to duplicate the error and not all machines with the same configuration report the same error. Any clues appreciated TIA Peter Back to top Display posts from previous: All Posts1 Day7 Days2 Weeks1 Month3 Months6 Months1 Year Oldest FirstNewest First         BorlandTalk.com Forum Index -> Delphi OLE Automation All times are GMT Page 1 of 1   Jump to: Select a forum C++ Builder Newsgroups----------------C++ BuilderC++ Builder (ActiveX)C++ Builder (Announcements)C++ Builder (Command Line Tools)C++ Builder DatabasesC++ Builder Databases (ADO)C++ Builder Databases (Desktop)C++ Builder Databases (InterBase Express)C++ Builder Databases (Multi-Tier)C++ Builder Databases (SQL Servers)C++ Builder (Graphics)C++ Builder (IDE)C++ Builder (Internet)C++ Builder (Internet Socket)C++ Builder (Internet Web)C++ Builder (Jobs)C++ Builder (Language)C++ Builder (Language C++)C++ Builder (Compatibility with MFC)C++ Builder (Native API)C++ Builder (Non-Technical)C++ Builder (Students)C++ Builder (Third Party Tools)C++ Builder (Upgrade)C++ Builder (VCL)C++ Builder (VCL Components Usage)C++ Builder (VCL Components Development)C++ Builder (VCL Usage)C++ Builder (WinAPI)C++ Builder Installation Delphi Newsgroups----------------Delphi (General)Delphi ActiveX Controls UsageDelphi ActiveX Controls DevelopmentDelphi As400Delphi DatabasesDelphi Databases (ADO)Delphi Databases (dbExpress)Delphi Databases (Desktop)Delphi Databases (InterBase Express)Delphi Databases (Multi-Tier)Delphi Databases (SQL Servers)Delphi DeploymentDelphi GraphicsDelphi IDEDelphi InternationalizationDelphi InternetDelphi Internet Isapi-WebBrokerDelphi Internet WebSnapDelphi Internet WinsockDelphi JobsDelphi Language BASMDelphi Language ObjectPascalDelphi Model Driven Architecture (General)Delphi Model Driven Architecture (Third Party)Delphi MultimediaDelphi Native APIDelphi Non-TechnicalDelphi ObjectPascalDelphi OLE AutomationDelphi OO designDelphi OpenToolsAPIDelphi Reporting-ChartingDelphi RTLDelphi StudentsDelphi TeamSourceDelphi Thirdparty ToolsDelphi Thirdparty Tools (General)Delphi Thirdparty Tools (IntraWeb)Delphi Thirdparty Tools (RaveReports)Delphi UpgradeDelphi VCLDelphi VCL ComponentsDelphi VCL Components UsingDelphi VCL Components WritingDelphi WebServices SOAPDelphi WinAPIDelphi XMLDelphi Installationcomp.lang.pascal.delphi.components.misccomp.lang.pascal.delphi.components.usagecomp.lang.pascal.delphi.components.writingcomp.lang.pascal.delphi.databasescomp.lang.pascal.delphi.misccomp.sources.delphi JBuilder Newsgroups----------------JBuilderJBuilder AnnouncementsJBuilder Applet IssuesJBuilder As400JBuilder CompilerJBuilder CORBA/RMIJBuilder DatabasesJBuilder DB SwingJBuilder DebuggerJBuilder DeploymentJBuilder DocumentationJBuilder EnterpriseJBuilder HandheldJBuilder IDEJBuilder JavaJBuilder JavaAPIJBuilder Java LanguageJBuilder Java SwingJBuilder Java BeansJBuilder Java Beans UsageJBuilder Java Beans DevelopmentJBuilder JBCLJBuilder JDataStoreJBuilder JobsJBuilder LinuxJBuilder MacintoshJBuilder & MobileSetJBuilder MultiLingual AppsJBuilder Non-TechnicalJBuilder OpenToolsJBuilder Servlets (JSP)JBuilder StudentsJBuilder Team DevelopmentJBuilder Thirdparty ToolsJBuilder UpgradeJBuilder Installation InterBase Newsgroups----------------InterBaseInterBase Bug DiscussionInterBase GeneralInterBase IBConsoleInterBase OpenSourceInterBase ReplicationInterBase SQLInterBase ThirdpartyInterBase Installation Miscellaneous Borland Newsgroups----------------AppCenterAppServerEnteraVisiBroker  You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum Powered by phpBB © 2001, 2006 phpBB Group SEO toolkit © 2004-2006 webmedic.