An overview of how to automate Outlook with Visual FoxPro.
5 thoughts on “Outlook Automation with VFP”
Hi. I’ve used the FIND command to find an email msg, task or appointment. What I have a pbm with is the very first time you initiate the find, it takes MINUTES. It acts like it’s indexing or something. Then after that initial find, the next time you try to find anything, bam! it finds it (or not) in less than 1 second.
Excellent article. Thank you for taking the time to write it. One other issue I’m having is I am (here we go again), finding a public folder and once I find it, I want to display it on screen. I have the object (ie oCalendarFolder) and when I call oCalendarFolder.Display it shows the window, but also returns an error “Display is not a member object”.
Forgive my ignorance. I’m new to this way of coding. Can you tell me the difference in what you’ve outlined in your white paper where you write: loApp = CREATEOBJECT(“OUTLOOK.APPLICATION”) loSpace = loApp.GetNameSpace(“MAPI”) loFolders = loSpace.Folders loItems = loSpace.Folders.Items
and the follwing:
LOCAL loOutlook, loHandler loOutlook=CREATEOBJECT( [Outlook.Application] ) loHandler=NEWOBJECT(“OutlookHandler”) EVENTHANDLER( loOutlook, loHandler ) SUSPEND DEFINE CLASS OutlookHandler AS session OLEPUBLIC IMPLEMENTS ApplicationEvents_10 IN {00062FFF-0000-0000-C000-000000000046}#9.1 PROCEDURE ApplicationEvents_10_ItemSend(Item AS VARIANT, Cancel AS LOGICAL) AS VOID * add user code here ENDPROC
Great question. The main difference is one of how you react to items. The first approach is useful for actively looking for items without worrying about what the user is doing. You aren’t told if there are new emails or new items added – it’s more if you are adding items automatically or reviewing existing items.
Using the IMPLEMENT approach, you are able to interact with what the user is doing. For example, when a new message comes in, your Outlook handler can react to it automatically. When a user clicks a button, you can react to it further. There’s more code required but more available actions to work from.
For example, if your application, wants to react to new messages as they come in, you would need to use the IMPLEMENTS approach.
Hi. I’ve used the FIND command to find an email msg, task or appointment. What I have a pbm with is the very first time you initiate the find, it takes MINUTES. It acts like it’s indexing or something. Then after that initial find, the next time you try to find anything, bam! it finds it (or not) in less than 1 second.
Ideas?
Excellent article. Thank you for taking the time to write it. One other issue I’m having is I am (here we go again), finding a public folder and once I find it, I want to display it on screen. I have the object (ie oCalendarFolder) and when I call oCalendarFolder.Display it shows the window, but also returns an error “Display is not a member object”.
Ideas?
How can Outlook be configured so when my vfp app wants to use it to email a file it doesn’t constanly ask if its ok?
Forgive my ignorance. I’m new to this way of coding.
Can you tell me the difference in what you’ve outlined in your white paper where you write:
loApp = CREATEOBJECT(“OUTLOOK.APPLICATION”)
loSpace = loApp.GetNameSpace(“MAPI”)
loFolders = loSpace.Folders
loItems = loSpace.Folders.Items
and the follwing:
LOCAL loOutlook, loHandler
loOutlook=CREATEOBJECT( [Outlook.Application] )
loHandler=NEWOBJECT(“OutlookHandler”)
EVENTHANDLER( loOutlook, loHandler )
SUSPEND
DEFINE CLASS OutlookHandler AS session OLEPUBLIC
IMPLEMENTS ApplicationEvents_10 IN {00062FFF-0000-0000-C000-000000000046}#9.1
PROCEDURE ApplicationEvents_10_ItemSend(Item AS VARIANT, Cancel AS LOGICAL) AS VOID
* add user code here
ENDPROC
Dan,
Great question. The main difference is one of how you react to items. The first approach is useful for actively looking for items without worrying about what the user is doing. You aren’t told if there are new emails or new items added – it’s more if you are adding items automatically or reviewing existing items.
Using the IMPLEMENT approach, you are able to interact with what the user is doing. For example, when a new message comes in, your Outlook handler can react to it automatically. When a user clicks a button, you can react to it further. There’s more code required but more available actions to work from.
For example, if your application, wants to react to new messages as they come in, you would need to use the IMPLEMENTS approach.
Make sense?