Mike & Doris Manning
mikedorism at adelphia.net
Mon Jun 28 15:11:32 CDT 2004
We ran into a similar problem because we have many different operating systems in our organization. We got around it by not referencing a particular Outlook object model. Doris Manning Database Administrator Hargrove Inc. www.hargroveinc.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin - Beach Access Software Sent: Monday, June 28, 2004 1:16 PM To: AccessD at databaseadvisors.com Subject: [AccessD] Outlook Object Broken Dear List: I provide an app to a client which uses the Outlook object to send emails. In my version the reference is to the Microsoft Outlook 9.0 Object Library. They recently upgraded to A2003 and their reference is now to the Microsoft Outlook 11.0 Object Library. When my app hits the line of code:Set objOutlook = CreateObject("Outlook.Application") it blows up saying it is unable to create the object. Is there an easy fix or workaround to this problem? MTIA, Rocky Smolin Beach Access Software http://www.e-z-mrp.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com