[AccessD] A2K: Runtime version of 2003 (Crap)

I have this little function that uses BLAT to email, this is what I've been using so I don't meet up with the problematic issues of SPx or SRx for Office... 

It's available at the following URL...
http://www.rogersaccesslibrary.com/OtherLibraries.asp#Tapia,Francsico

-- 
-Francisco


John W. Colby wrote:

>If you truly think that SP3 has anything at ALL to do with enhancing
>security (other than Microsoft's) you are delusional.  SP3 does nothing to
>prevent a virus from running on your machine.  It does nothing to prevent
>Access from using VBA to form a virus and scramble the user's data, or watch
>for passwords and credit card numbers and email them out to an address NOT
>in the address book.
>
>On the other hand, it absolutely does trash an application that my client
>paid me to write for them.  It prevents using Outlook automation to send
>mail in many instances.
>
>IOW, it does NOTHING AT all to enhance the security of my client, while
>causing a perfectly valid application to stop working.
>
>I mean a class action lawsuit for doing nothing to enhance security while
>screwing up valid applications, trashing code modules then hiding the fact
>that they were causing these problems, denying that anything was wrong, and
>causing me to waste a TON of time trying to figure out why my applications
>were corrupting form modules, then having the BALLS to force me to come
>begging them to give me a fix to the problem that they already had and
>weren't telling anyone they had.
>
>I mean THAT kind of class action lawsuit.
>
>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 12:19 PM
>To: Access Developers discussion and problem solving
>Subject: RE: [AccessD] A2K: Runtime version of 2003 (Crap)
>
>
>You mean as opposed to a class action lawsuit for not providing adequate
>security? <g>
>
>Charlotte Foust
>
>-----Original Message-----
>From: John W. Colby [mailto:jcolby at colbyconsulting.com]
>Sent: Friday, December 05, 2003 9:10 AM
>To: Access Developers discussion and problem solving
>Subject: 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
>
>
>_______________________________________________
>  
>