- In Outlook, I went to File, then Office Account, then clicked "About
Outlook"
- Near the top of the resulting screen I saw "Microsoft Outlook for Office
365 MSO (16.0.11929.20618) 64-bit" (and of course there were "TM"s spread
around in that string).
- Then I went to VFP and opened up the code I had used a while back. The
'basic' design of it is as follows:
oOutlook = CREATEOBJECT('outlook.application')
...
oMsg = oOutlook.CreateItem(0)
oMsg.to = <email address>
oMsg.from = <the from address>
oMsg.subject = <some subject line>
oMsg.htmlbody = <my email message, a fantastically formatted and
built/styled HTML message I might add.... :) >
*-- maybe there was another step or two - but you get the gist
*-- then actually sent the message.
oMsg.send()
I did the above this past Friday (4/17/2020) - grabbing out some of that
code and ran lines of it from the VFP command prompt (the actual code would
have sent out about 100 emails for a 'crisis' situation that did not exist
so I did not want to trigger that - heh). But the email I created with the
above process was sent and delivered (to myself at a couple different email
addresses I have). According to the "About" VFP - I am using VFP SP2,
version 09.00.0000.5815.
Of course, this was ONLY Outlook. It was not Word, Excel, or Powerpoint.
But it does clearly call itself 64-bit. Now.... based on MS's past behavior
I certainly do not expect them to be honest. But trying to deceive at this
level would seem a little ridiculous even for them.
I will add that I do not know if we perhaps started with 32-bit Office at
one point and then migrated to 365 64-bit. This particular PC was set up
about 11 months ago. And given MS's poor history of cleaning up after
itself, there may be 32-bit libraries hanging around.
Note that I have installed 32-bit MS SQL ODBC drivers on the machine. I
kind of doubt that would have an impact, but its hard to tell without a lot
of library-calls tracking work (which I do not feel like doing...).
I have some Powerpoint automation code around here somewhere. Maybe I'll
give that a try too.
But the thing that started this whole thread was whether or not the "VFP
10" (64bit VFP?) version would be able to do automation into "64bit" Office
stuff. So even if my 32-bit example is 'magic' are we still thinking the
64bit VFP would not work with 64bit Office?
Maybe it would be worth sharing/creating several code samples that we have
used for 'Office automation', store them somewhere, and then use those as a
quick-test set for any new VFP release or compatible product...
-Charlie
On Sat, Apr 18, 2020 at 1:40 PM Jürgen Wondzinski <[email protected]>
wrote:
> Are you absolutely sure that you have Office 64bit installed? Since it's
> not
> only me, but MS itself to state that it's technically impossible, I really
> doubt it. :) If yes, you would be the first to made it magically happen.
>
> wOOdy
>
>
> -----Ursprüngliche Nachricht-----
> Von: ProFox <[email protected]> Im Auftrag von Charlie Coleman
> Gesendet: Samstag, 18. April 2020 18:36
> An: ProFox Email List <[email protected]>
> Cc: [email protected]
> Betreff: Re: Office automation using VFP 10 64-bit version
>
> Not to beat this to utter death and disfigurement...
>
> I definitely used Automation from 32-bit VFP into 64-bit Outlook. So are we
> saying that if I go to 64-bit VFP (the "VFP 10") that suddenly that same
> code would not work?
>
> -Charlie
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message:
https://leafe.com/archives/byMID/CAJGvLx2gRK9jB0=38JrYDKKfNWmMMM5=tdfeaagzpzwtoej...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
