Joe Rojas
JRojas at tnco-inc.com
Tue Jan 18 15:36:30 CST 2005
(Office 2000 w/all SPs) I have an Access application that sends out task requests. If I use the OOM, everything works find but I have to deal with the annoying security alerts. When I tried to use Redemption to send the task requests, the recipient receives the task request but cannot open it. The recipient receives either a "Can't open item" error or and error that says something about an invalid property and cannot be opened. I have been working with Dmitry for quite sometime and he appears to be stumped. I was so close to converting my app to Redemption. :( Anyone else have this problem? JR -----Original Message----- From: Andy Lacey [mailto:andy at minstersystems.co.uk] Sent: Tuesday, January 18, 2005 2:31 PM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Outlook object model security Us too. Share the problem Joe. BTW the other solution is ClickYes http://www.contextmagic.com/express-clickyes/ but it's not so elegant. Flashes up the Outlook security prompt and then goes away again. -- Andy Lacey http://www.minstersystems.co.uk > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of > Charlotte Foust > Sent: 18 January 2005 17:44 > To: Access Developers discussion and problem solving > Subject: RE: [AccessD] Outlook object model security > > > What kind of snag? We use redemption with our applications > and have had no problems, or is this OL2003? If so, I'd like > to be aware of the pitfalls. > > Charlotte Foust > > > -----Original Message----- > From: Joe Rojas [mailto:JRojas at tnco-inc.com] > Sent: Tuesday, January 18, 2005 9:28 AM > To: 'Access Developers discussion and problem solving' > Subject: [AccessD] Outlook object model security > > > I was trying to use Redemption to get around the outlook > object model's annoying security alerts but ran into a snag > that seems to have stumped even Dmitry. With that said, does > Microsoft provide any type of mechanism to bypass the > security for people who make legitimate Access applications? > > Thanks, > JR > > > > This electronic transmission is strictly confidential to > TNCO, Inc. and intended solely for the addressee. It may > contain information which is covered by legal, professional, > or other privileges. If you are not the intended addressee, > or someone authorized by the intended addressee to receive > transmissions on behalf of the addressee, you must not > retain, disclose in any form, copy, or take any action in > reliance on this transmission. If you have received this > transmission in error, please notify the sender as soon as > possible and destroy this message. While TNCO, Inc. uses > virus protection, the recipient should check this email and > any attachments for the presence of viruses. TNCO, Inc. > accepts no liability for any damage caused by any virus > transmitted by this email. > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com This electronic transmission is strictly confidential to TNCO, Inc. and intended solely for the addressee. It may contain information which is covered by legal, professional, or other privileges. If you are not the intended addressee, or someone authorized by the intended addressee to receive transmissions on behalf of the addressee, you must not retain, disclose in any form, copy, or take any action in reliance on this transmission. If you have received this transmission in error, please notify the sender as soon as possible and destroy this message. While TNCO, Inc. uses virus protection, the recipient should check this email and any attachments for the presence of viruses. TNCO, Inc. accepts no liability for any damage caused by any virus transmitted by this email.