Brock, Christian T, HRC-Alexandria
Christian.Brock at hoffman.army.mil
Tue Dec 9 13:20:04 CST 2003
If you send the email in html format, outlook security (Outlook 2002 on Windows XP) will let it through without any problems. Christian Brock -----Original Message----- From: MartyConnelly [mailto:martyconnelly at shaw.ca] Sent: Tuesday, 09 December 2003 13:59 To: Access Developers discussion and problem solving Subject: Re: [AccessD] A2K: Runtime version of 2003 (Crap) This might be an easier method of overcoming the Outlook security sending mail without requiring multiple clicks. Haven't tried it but it looks easier than using Redemption method. Express ClickYes Puts an Icon in systray that captures the outlook messages You can modify behaviour with VBA code. http://www.express-soft.com/mailmate/clickyes.html Erwin Craps - IT Helps wrote: >Yes Brett I can, or at least point you at it > >There is a MSKB article on it... >Looking for it....... Found. >Luckaly I safe often used HTML pages to my disk (they sometimes disapear >from the MS site...). >Have to turn this *@s*## each time of when installing Exchange server. >Here it is, knock yourself out :-) >http://support.microsoft.com/default.aspx?scid=kb;en-us;q290499 > >Please note that you can only turn security off when having outlook >connected to Microsoft Exchange Server!!! >Outlook checks a form with settings in the public folder of Exchange. >So this does not work if your Outlook only uses PST files. > >Read the installation procedure tree times before actualy dooing it. >Had some misunderstandings the first time I done this (now several years >ago). > > >The principle is that you register a form in MSEX public folder where >you change the security settings. Some files (1 or 2) need to be >put/replaced in the winnt system32 folder of the Exchange server. > >A registry key must be added on each Outlook client pc. >This key tells Outlook to look for the security setting in the form in >the public folder and to use those for outlook. >This way you can free exe files (for example) or allow doubleclick from >the e-mail for files. >Also the automation pop-ups can be avoided using this procedure. > > >Greetz >PS: Thats my second good deed of the day.... > > > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Brett >Barabash >Sent: Monday, December 08, 2003 3:20 PM >To: 'Access Developers discussion and problem solving' >Subject: RE: [AccessD] A2K: Runtime version of 2003 (Crap) > >Erwin, >Can you give me some more info about this? Enquiring minds want to >know. > >-----Original Message----- >From: Erwin Craps - IT Helps [mailto:Erwin.Craps at ithelps.be] >Sent: Monday, December 08, 2003 1:48 AM >To: Access Developers discussion and problem solving >Subject: RE: [AccessD] A2K: Runtime version of 2003 (Crap) > > >This Outlook automation security thing is pretty easy solvable when >using Outlook combined with Exchange server. >There is a form that needs to be installed in the public Exchange folder >and a registry key on each machine. >By this you can turn of several security issues (like blocking some file >type and automation). >I use Outlook automation for several years now without any problem >(except for a "send as" bug in O2K3). > >Ofcourse your network needs to be protected with other means if you turn >of Outlook security. >But a network protection should be a default issue when having Exchange >server. > > >Erwin > >-----Oorspronkelijk bericht----- >Van: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com] Namens John W. Colby >Verzonden: vrijdag 5 december 2003 18:10 >Aan: Access Developers discussion and problem solving >Onderwerp: RE: [AccessD] A2K: Runtime version of 2003 (Crap) > >I'm simply pointing out that installing SP3 is not a panacea for the >problem you are discussing. Many developers don't use Outlook >automation so they don't care. If they DO use it however, that portion >of their app is trashed just by updating to SP3. > >I personally have lost an estimated 60 hours to this problem over the >last few years. I'd LOVE to participate in a class action lawsuit to >recover my lost wages. > >John W. Colby >www.ColbyConsulting.com > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte >Foust >Sent: Friday, December 05, 2003 11:58 AM >To: Access Developers discussion and problem solving >Subject: RE: [AccessD] A2K: Runtime version of 2003 (Crap) > > >That's an automation problem, John. There are workarounds (like >Redemption or using SMTP mail) and it isn't a fair comparison anyhow. >Installing SR3 will *break* the apps by popping up the security dialogs >when you try to send mail automatically, but it won't destroy them. NOT >installing SR3 when you have 2002 or 2003 apps also installed *can* >destroy a 2000 Access database. > >Charlotte Foust > >-----Original Message----- >From: John W. Colby [mailto:jcolby at colbyconsulting.com] >Sent: Friday, December 05, 2003 8:50 AM >To: Access Developers discussion and problem solving >Subject: RE: [AccessD] A2K: Runtime version of 2003 (Crap) > > >Installing SP3 will also toast any apps which try to use Outlook to send >mail using the address book. > >8-( > >John W. Colby >www.ColbyConsulting.com > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte >Foust >Sent: Friday, December 05, 2003 11:37 AM >To: Access Developers discussion and problem solving >Subject: RE: [AccessD] A2K: Runtime version of 2003 (Crap) > > >As Mike Groh's editorial, referenced in your other post, indicates, you >appear to have run afoul of the conflict between the O2k version of the >vbe6.dll and the version installed with any MS 2002 app. It apparently >also happens if you install a 2003 app, which makes sense. The cure is >to patch the 2000 MSAccess.exe, and it always annoyed me that being >broken by a later version was considered a bug in *2000*!! Installing >SR-3 should cure the bug, but it won't recover any database that got >toasted by the problem. > >Charlotte Foust > >-----Original Message----- >From: Darren DICK [mailto:d.dick at uws.edu.au] >Sent: Thursday, December 04, 2003 6:07 PM >To: AccessD List >Subject: [AccessD] A2K: Runtime version of 2003 (Crap) > > >Hello all >I recently installed the runtime version of Access 2003. > >This piece of crap has taken over and now all my access apps open in a >2003 shell. I keep getting error messages about the potential damage the >code within the dB can cause and am prompted each time I open a dB if I >wish to continue or cancel > >I have tried unsuccessfully to remove Access 2003 Runtime from Control >Panel. at least on 4 occasions. I have re-installed Office and Access >2000 - Still no joy. So I deleted the folder (though not all files. >'Cause Widoze had ' em opened I presume) > >On top of all that I getting very strange errors each time I open a db >or try to view the code for an even or control. Error message as >follows. (This message would appear even before I deleted the folder - >yes I have re-booted many times) >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >Microsoft Visual Basic (Msgbox Caption) >Error Accessing File. Network Connection May have been lost >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Anyone seen this or better still anyone got a solution? > >Many thanks in advance > >Darren > > >_______________________________________________ >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 >_______________________________________________ >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 email and any files transmitted with it are confidential and >intended solely for the use of the individual or entity to whom they are >addressed. >If you have received this email in error please notify the originator of >the message. This footer also confirms that this email message has been >scanned for the presence of computer viruses. > >Any views expressed in this message are those of the individual sender, >except where the sender specifies and with authority, states them to be >the views of Tappe Construction Co. > >Scanning of this message and addition of this footer is performed by >SurfControl E-mail Filter software in conjunction with virus detection >software. > >_______________________________________________ >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 > > > -- Marty Connelly Victoria, B.C. Canada _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com