On Wed, 17 Sep 2003 17:14:06 +0100, "Nigel Lawrance"
<na*@exeter37.freeserve.co.uk> wrote:
I've just read your earlier posts relating to this.
They don't make complete sense to me.
What is the end game here?
Nigel
Oh phooey. I'm having to implement a hodge-podge of
techniques to achieve a rather simplistic goal. There's
a huge amount of coding in an old Access 2.0 application
that has run RELIABLY under Windows XP since the OS
was released. Revising that working app to a modern
32-bit release of Access is not currently an option. A
missing feature is desired to be added enabling the
Access 2.0 app to email report images or RTF's and it is
that which we're trying to achieve.
This has been a challenge. A host of obstacles has
been thrown into the pot...
1) a past installation of Microsoft's Q330994 security
patch for Outlook Express hindered total automation
of the process. Even removing the patch through the
Control Panel facility was NOT effective.
2) DoCmd SendObject A_REPORT, "Report6", A_FORMATRTF, "JJ@MyISP.net",
, , MySubject, MyBodyText, 0 turned out to be completely unreliable
in creating an RTF type attachment that could be opened and read
by the intended recipient.
3) Microsoft Outlook does not support DDE. Unfortunately,
with the A20 app, DDE is about the best option available to
us and so we're forced to work with OutLook Express, DDE,
and SendObject.
I've been thinking about doing a separate Access 97 app,
attaching to the tables in the Access 2.0 app for read functionality
only and trying to implement the desired functionality using A97 and
Microsoft OutLook. I understand that 97 cannot write to A20 tables
but can read them. Of this, I'm uncertain. At any rate, we've put a
lot of effort into revising the A20 app and I'm determined to make
it work if at all possible.