outlook to access: follow up

darbid,

if you are ever in London, or if I'm in Munich, I owe you many,many beers...thank you very much for your help and your patience.
 
Congratulations and maybe i just will.

One word or warning. Outlook objects must be set to nothing. Further if you have the main Outlook application set to an object then you must set this to nothing last.

While your testing you should check your Task Manager after closing outlook and access to make sure that they are both closing properly.
 
I think I understand what you mean. I would like to ask though, should the Outlook that this script is running under be independant of any other incoming mail.

For e.g. if we have a customer called Bob and he sends us an email not related to an order, I presume the outlook script will still run and embed the various components into the Access form.

Should I then rather keep that particular Outlook instance separate and forward emails to the recipients?
 
I think I understand what you mean. I would like to ask though, should the Outlook that this script is running under be independant of any other incoming mail.

For e.g. if we have a customer called Bob and he sends us an email not related to an order, I presume the outlook script will still run and embed the various components into the Access form.

Should I then rather keep that particular Outlook instance separate and forward emails to the recipients?
No you do not need another Outlook. You said you had a Rule set up for when to move an incoming mail to the Orders folder.

In the Items Add event you need to code that rule in there and check the item that has been added. If it meets the criteria then and only then send it to Access. Of course you could send it to access and do your criteria checking there. The reason you would do this in Outlook is that it might prove easier to move it to the Orders folder and it would do this checking without access popping up and being used.

So your steps as I would see them is as follows;

Outlook tells you a new email has come in.
Check the email for special contents or whatever your criteria are
If True - move to orders folder - send to Access
If false just skip the above
 
Hi,

I didn't explain fully.

I have 1 exchange server, let's call it "server1". I have 1 database/sql server, let's call it server2. I have 3 workstations that need to be aware of specific incoming mail as well as the day-to-day stuff. I have 3 potential scenarios:-

1. I can install Access & Outlook and configure an "Orders" mailbox on server2 to intercept orders email, put the required information into the sql db and send an email alert to the workstations

2. I can use a rule (as I currently have for testing purposes) specifying that any incoming mail with the word "order" in the subject or body gets forwarded to the workstations. You can probably see the flaws in this concept.

3.As per 1. above, I can set up an Orders mailbox on server1 so that any orders will go there. This mailbox can then be duplicated on each workstation with a rule that any mail going into that mailbox fires the Outlook code which launches Access on the workstations and causes the NewOrders form to pop up although I am not sure about the coding implications of this, I think the listener would have to be told to only respond to that particular mailbox as opposed to all incoming mail.

At the moment (and without sufficient testing at this point) I am leaning towards option 3.
 

Users who are viewing this thread

Back
Top Bottom