Erwin Craps - IT Helps
Erwin.Craps at ithelps.be
Mon Dec 8 01:48:18 CST 2003
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