Yeah!
+1
Nice one Ted! Touche!
-K-
On 9/4/2019 12:22 PM, Richard Kaye wrote:
Roflmao...
--
rk
-Original Message-
From: ProfoxTech On Behalf Of Ted Roche
Sent: Wednesday, September 4, 2019 3:01 PM
To: profoxt...@leafe.com
Subject: Re: Outlook Redemption tool
Error 0xOldFart
Roflmao...
--
rk
-Original Message-
From: ProfoxTech On Behalf Of Ted Roche
Sent: Wednesday, September 4, 2019 3:01 PM
To: profoxt...@leafe.com
Subject: Re: Outlook Redemption tool
Error 0xOldFart: The memory could not be "read"
On Wed, Sep 4, 2019 at 1:15 PM Kurt @ Gm
Error 0xOldFart: The memory could not be "read"
On Wed, Sep 4, 2019 at 1:15 PM Kurt @ Gmail wrote:
> Awesome - I'm glad Gianni's suggestion worked. I am quite sure I also
> used that .Display() option before. But, again - it was SO Many Years
> ago - and, at my advanced age - Memory Leakage is
Awesome - I'm glad Gianni's suggestion worked. I am quite sure I also
used that .Display() option before. But, again - it was SO Many Years
ago - and, at my advanced age - Memory Leakage is quite
common... :-)
-K-
On 9/4/2019 6:41 AM, MB Software Solutions, LLC wrote:
PERFECT!!!
On 9/4/2019 5:40 AM, Alan Bourke wrote:
The security issues only applied (I think) to trying to automate Outlook via
Simple MAPI. Extended MAPI, which Craig Boyd's VFPEXMAPI.FLL uses, and MAPI via
the Outlook Object Model as you have used, were never a problem in this regard.
Thanks for
PERFECT!!! That did it!
On 9/3/2019 9:39 PM, Gianni Turri wrote:
Use .Display() instead of .Save()
Gianni
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
___
Post Messages to:
Kurt,
you could be correct that send(.t.) may just send it. I do have some
code that uses it to display the message prior to it being sent, but
looking back at the code now, it is referring to a messages object, not
a mailitem as in Mike's code, so maybe there is a difference but it's
easy
The security issues only applied (I think) to trying to automate Outlook via
Simple MAPI. Extended MAPI, which Craig Boyd's VFPEXMAPI.FLL uses, and MAPI via
the Outlook Object Model as you have used, were never a problem in this regard.
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
Cool! Yeah - my bad guess - but, hopefully - Gianni is RIGHT!!!
Go for it Mike!
-K-
On 9/3/2019 6:39 PM, Gianni Turri wrote:
Use .Display() instead of .Save()
Gianni
On Tue, 3 Sep 2019 19:41:02 -0400, "MB Software Solutions, LLC"
wrote:
No, there's no visible property. I had checked
Use .Display() instead of .Save()
Gianni
On Tue, 3 Sep 2019 19:41:02 -0400, "MB Software Solutions, LLC"
wrote:
No, there's no visible property. I had checked that prior to posting.
On 9/3/2019 7:14 PM, Kurt at VR-FX wrote:
> Frank - I think what you suggested would Send it. He simply wants
No, there's no visible property. I had checked that prior to posting.
On 9/3/2019 7:14 PM, Kurt at VR-FX wrote:
Frank - I think what you suggested would Send it. He simply wants it
on the screen to view. I think its possible that the window is Hidden
some how. Must be a way to place it on
Frank - I think what you suggested would Send it. He simply wants it on
the screen to view. I think its possible that the window is Hidden some
how. Must be a way to place it on top.
I've done this kinda stuff in the past - using the same book at examples
in it. But, I'm confounded at the
Off the top of my head (and is been a long time since I did this) but try
passing true to the send (.t.) I think that might display the email ready to be
sent.
On 3 September 2019 16:53:17 GMT-04:00, "MB Software Solutions, LLC"
wrote:
>I have a need to use MAPI (yes, I know Ted et al: MAPI
13 matches
Mail list logo
