Michael:
Doesn't work...
Outlook express is on some boxes and outlook 2000 is on others.
With Exchange 2007 you need Outlook 2003 or better. Don't have it and can't buy
it. We are using OWA (Outlook Web Access) which seems ok.
CDO was a good choice because you could authenticate with it. But the exchange
box rejected it with invalid user (even though it was correct). I don't have
access to the exchange box and the folks that were supposed to help
couldn't/wouldn't.
Here is some CDO code I tried:
clear
on error do error_hand
use s_email
loMessage = Createobject("CDO.Message")
loConfiguration = Createobject("CDO.Configuration")
lcSchema = "http://schemas.microsoft.com/cdo/configuration/";
With loConfiguration.Fields
.Item(lcSchema + "postusing") = 1
.Item(lcSchema + "smtpserver") = our_mail_server
.Item(lcSchema + "smtpserverport") = 25
.Item(lcSchema + "smtpconnectiontimeout") = 30
.Item(lcSchema + "smtpAccountName") = "account name here"
.Item(lcSchema + "sendemailaddress") = "sender email address"
.Item(lcSchema + "sendusername") = "sender name"
.Item(lcSchema + "sendpassword") = "passwrd here"
.Item(lcSchema + "sendusing") = 2
.Item(lcSchema + "smtpauthenticate") = 1
.Item(lcSchema + "smtpusessl") = .f. &&do not use SSL
.Update()
ENDWITH
With loMessage
.Configuration = loConfiguration
.organization = "NJ Devils Hockey Club"
.FROM = from_email_address
.to = to_email_address
.Subject = "Test Email From CDO - test 3 auth = 1"
.TextBody = s_email.e_text &&from DB field...
.Addattachment("C:\Canon Olympus Camera\Salmon Flies\BlackDose.jpg") &&to
add an attachment or a group of attachments
.fields("urn:schemas:httpmail:Importance") = 2 &&changes the header in the
email but does not change the importance or priority...bug???
.fields("urn:schemas:httpmail:Priority") = 1
.fields.update()
.Send()
ENDWITH
loMessage = null
loConfiguration = null
use
return
procedure error_hand &&error 1429 will be triggered if an error in the send
dimension gaError(7) &&7 rows is returned in AERROR()
for i = 1 to 7 &&clear the error array
gaError(i) = ""
endfor
aerror(gaError) &&load the error parameters
? gaError(3) &&gaError(i,3) will have the simplified error message
*_cliptext = gaError(3)
return .f.
How do the rest send email form VFP to an exchange box?
Regards,
Jack
________________________________________
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Michael Madigan [EMAIL
PROTECTED]
Sent: Wednesday, October 01, 2008 4:24 PM
To: [EMAIL PROTECTED]
Subject: RE: Disable Mouse When A Form Is Visible
What about just automating Outlook?
--- On Wed, 10/1/08, Jack Skelley <[EMAIL PROTECTED]> wrote:
> From: Jack Skelley <[EMAIL PROTECTED]>
> Subject: RE: Disable Mouse When A Form Is Visible
> To: "profox@leafe.com" <profox@leafe.com>
> Date: Wednesday, October 1, 2008, 4:19 PM
> Paul:
> Warning my users would make them want to mess it up all the
> more! I love these guys but all have been hit in the head
> with sticks and pucks their entire life.
> You are absolutely correct about the fragile application.
> I tried using CDO to send email to our exchange server but
> the mail was rejected. Plus I have tried too many other ways
> to send mail that doesn't work either.
> What does work is to launch the web access version of the
> exchange box and send mail that way. But it involves
> multiple windows that are touchy as to what window is
> getting the info. Especially when attachment windows appear.
> I tried making the window hidden but then the data transfer
> does not take place. Apparently the window must be on top to
> receive the data.
> Thanks for the suggestions.
> Regards,
>
> Jack
>
>
> ________________________________________
> From: [EMAIL PROTECTED]
> [EMAIL PROTECTED] On Behalf Of Paul McNett
> [EMAIL PROTECTED]
> Sent: Wednesday, October 01, 2008 3:01 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Disable Mouse When A Form Is Visible
>
> Jack Skelley wrote:
> > This is what modal is for when you have a pure VFP
> app. But in my case this is not true. There are other open
> apps that VFP is 'talking to' as long as the current
> window doesn't change all is good. But if user activates
> another window and I am trying to load window 'x'
> and window 'y' becomes active all quickly goes down
> hill.
> > I am sure that my users do not know alt+tab as a kbd
> shortcut...
> > Ok on the message box idea.
> > Thanks for any ideas you have.
>
> If a mouse gets an electric shock when it grabs food from
> slot b, it
> learns to grab food from slot a instead.
>
> So if really bad things happen if a user doesn't wait
> for a process to
> finish, why not warn them with a message box and then if
> they forget,
> that really bad thing will happen which will keep them from
> doing it
> again in the future.
>
> But I'd go back to the source of the problem. What
> about the design is
> so fragile that it can't stand user interaction?
> I'd fix that design
> problem instead of the symptom. So for instance, if you are
> interacting
> with an IE window and it would be bad for the user to close
> that window
> or pull up a different web page, you could disable it or
> make it
> invisible for the critical time of the process. Or
> something.
>
> Paul
>
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** 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.
