Re: Outlook version problem?
Welcome to the Forums.
I assume that this is Outlooks VBA code and not VB code automating Outlook.
One thing to check is if the other users have their security setting set to medium so they can choose to run
your code or not. If it was set to high then the code will not run.
Another note is that in Outlook XP the .SaveAsFile is a protected method and will incur the infamous Security Popup Prompt.
Re: Outlook version problem?
I've talked to some of my colleagues about the problem and the security settings are all at medium. Someone stated something about including a Outlook 2002 reference in the code. Do you know anything about this and how I could implement it? Thanks!
And could it also be a problem with my Exchange Server having multiple email addresses for different people. I'm thinking the lookup could bring up some kind of error when it returns multiple emails, assuming VBA would do this. Please let me know your thoughts.
Justin
Re: Outlook version problem?
Is this VB6 or Outlooks VBA Editor?
If its the editor then there is no need to include a reference to itself. I think
what you need to start with is some degugging.
Try adding some logging code to write some properties/variable values to a
text file.This way you can actually see what is happening or not happening
and why.
Re: Outlook version problem?
I'm using the Outlook VBA editor. I've tried taking everything out of the CommandButton2.Click() function and just adding a messagebox but nothing is happening. I keep clicking on the commandbutton2 and absolutely nothing happens, just like when all the code was there. What in the world could be going on here? Btw, The Commandbutton2 is on the "Read Page". The compose page works just fine. Thanks again for your help.
Justin
Re: Outlook version problem?
This custom form is a Published form or are you just copying it over to the other users machines?