Re: Sending Email From Access 2003, and Security Warning Popup

I thank you for the help and I'm looking over the click yes.

It is an interesting question whet

It is an interesting question whether or not Access Visual Basic procedures
belongs in a Macro discussion group. First, I have looked at the topics of
the Access Group and I do believe that this group is the most correct place
for Visual Basic procedures. When I review the issues under programming that
does not appear to be surrounding the topics I’m working with.

When I first started programming in Access I started with the “Macro
Language.” The more I read and studied most of the experts of the time Access
95 ant Access 97 recommended that the Visual Basic components were the
‘better’ way to handle macros. At that time I believed that both the Macro
language and Access Visual Basic Code were basically equivalent at least with
respect to a statement that they were both “macro”. I was also coming from
another programming language that used the word macro.

It was good advice; Access Visual Basic Code that I wrote in Access 97 has
worked extremely well through the Access 2000, Access XP and for the most
part Access 2003. Now I’m having some problems with AppActivate and Outlook
controls. When reading Access 2003 migration documentation Microsoft seems
to indicate that “Macros.” Would not work as they once did. I was very
pleased and surprised to find that the Access Visual Basic for the most part
has been forwards and backwards compatible.

My definition of macro comes from Microsoft Excel, Lotus and Enable Software
packages. There they use keystroke recorders and command codes for the most
part to accomplish specific tasks. If you use the record a macro button in
Microsoft Excel you will end up with a Visual Basic procedure. Therefore,
narrowly defining a macro as only “Access Macro Procedures” is provincial and
far to narrow even with respect to Microsoft Office integrated products.

My expertise, if I have any, is using the power of Access Visual Basic and
Access Tables to control other windows based applications. For example, I use
Access to audit, input and query SAP R/3, Outlook, legacy Telnet
applications, and flat data txt files used by my organization. These visual
basic commands do actually open other Windows based application and Send
Keystrokes to other applications.

You also seem to indicate that this is may be more appropriately an Outlook
security issue and not an Access 2003 issues. Here, I respectfully disagree.
I’m converting Access 97 code to Access 2003 code and trying to maintain
functionality. We have approximately 800 employees that routinely were sent
customized emails for updating contacts, validating work phone numbers, and
communicating with managers. Properly coded work allows us to customize the
language (subject and body) and send specialized query data as attachments.
The variables are all table driven. The power is in Access not Outlook. The
failure is in Access 2003 integration versus Access 97 integration with
Outlook which worked. In fact Microsoft lumps most of my favorite commands
as “Macro Security Risks”

I have spent several days working on the subtleties of the Outlook
integration issue of Access 2003 and Windows XP. At this point I’m going to
recommend that we keep several of our older computers in the previous desktop
stand of Access 97 and Windows 98 in order to preserve vital functionality
that Outlook Security Patches and Windows XP have emasculated. We have
already found that Access 97 will coexist on a Windows XP machine side by
side with Access 2003. I am very unhappy and frustrated that these functions
do not work inside our own firewall, with our own exchange server for email
addresses within our own domain. My network has authenticated my login and
the exchange server has been authenticated. Why can’t my own organization
trust that I am who I’m supposed to be and send emails? This trusted signor
is one thing for individual’s outsiders of our Microsoft Windows Server 2003.
With a C2 security rating or better I’m still not permitted to send email by
code?


"Steve Schapel" wrote:

> SacCourt,
>
> Another third-party utlilty which I know others have used successfully
> is available here...
> http://www.contextmagic.com/express-clickyes/
>
> Having said that, this is a macros newsgroup, and your question is not
> related to macros, in fact you are using a VBA procedure here. And in
> addition, it is really an Outlook security issue anyway, rather than
> being Access-related, in which case a [post to an Outlook newsgroup may
> get you a more authoritative response.
>
> --
> Steve Schapel, Microsoft Access MVP
>
>
> TPratt wrote:
> > I am currently using Outlook Redemption within a Microsoft Access Module
> > (Visual Basic) and it works beautifully.
> >
> > Good luck in your search...
> >
> >
>
.

Quantcast