2003 & 2007 on same machine

  • Thread starter Thread starter Guest
  • Start date Start date
Hi Secret,

Okay, a couple of comments...
When I fire this in A2000 I get no warning message from Outlook.
Click to expand...

What service pack level do you have Office 2000 patched to? I'm fairly
certain that if you have installed SP-3 that you will be treated to these
warning messages.
This is what I tested in A2007 and got no warning message.
Click to expand...

Since you are not using SendObject, my earlier statement about using the
EditMessage parameter does not apply.

Earlier, you wrote: "The only versions I am looking to run are 2000, 2003,
and 2007." Without using separate physical PC's, or Virtual PC, your only
option to install multiple versions of Outlook (in order to test your code
with the same version of Outlook, to mimic a customer's setup accurately)
would be to configure separate boot drives. The reason I say this is that it
is impossible to install more than one version of Outlook on a given bootable
partition.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

Secret Squirrel said:
I've pasted some code that I am using currently in my db. This code is behind
one of my forms. When I fire this in A2000 I get no warning message from
Outlook. When I fire it in A2003 I get the warning message. I'm using "Click
Yes" to get around this in 2003. This is what I tested in A2007 and got no
warning message.

Sub SendMessageGenerateTicket(Optional AttachmentPath)
Dim objOutlook As Outlook.Application
Dim objOutlookMsg As Outlook.MailItem
Dim objOutlookRecip As Outlook.Recipient
Dim objOutlookAttach As Outlook.Attachment
Dim db As Database
Dim rsEmail As Recordset
Dim stTo, stFrom, stCC, stBCC, stSubject, stSal, stText As String
Dim stQuery As String
Dim stAttachPath As String


stSubject = "RMA#: " & Forms![2005 Form]!RMA
stText = "The Disposition for the RMA noted in the subject line has been
completed. Please generate an 'R' ticket. The original WO# is: " &
Forms![2005 Form]![WO # - Line #]

'Create the Outlook session.
Set objOutlook = CreateObject("Outlook.Application")
'Create the message.
Set objOutlookMsg = objOutlook.CreateItem(olMailItem)
With objOutlookMsg
.To = Forms![2005 Form]![GenerateTicket].Column(2)
.Subject = stSubject
.Body = stText
.Importance = olImportanceNormal ' Normal Importance
.Send
'Next

End With
Set objOutlookMsg = Nothing
Set objOutlook = Nothing

End Sub

Tom Wickerath said:
Here's one way, but I was making the assumption that you are using the
SendObject method, which may not be the case. Type "DoCmd.SendObject"
(without the quotes) into a procedure. Then select this word and press the F1
button to open context-sensitive Help. You should see the following:

The SendObject method carries out the SendObject action in Visual Basic.

expression.SendObject(ObjectType, ObjectName, OutputFormat, To, Cc, Bcc,
Subject, MessageText, EditMessage, TemplateFile)

and

EditMessage Optional Variant. Use True (–1) to open the electronic mail
application immediately with the message loaded, so the message can be
edited. Use False (0) to send the message without editing it. If you leave
this argument blank, the default (True) is assumed.

So, if you left this argument blank, you'd get True, which should result in
the message being opened in Outlook and available for you to edit (requires
you to press the Send button).


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
Click to expand...
Click to expand...
 
I'm running Office 2000 with SP-3 (9.0.8948). We're all using that SP at work
and nobody has ever gotten that warning message. When I use it on my home pc
(which has the 2003 version), I get that warning message. And then I just
tested it with A2007 and didn't see any error messages. Should I be getting
this message with all versions or am I a lucky guy?

Tom Wickerath said:
Hi Secret,

Okay, a couple of comments...
When I fire this in A2000 I get no warning message from Outlook.
Click to expand...

What service pack level do you have Office 2000 patched to? I'm fairly
certain that if you have installed SP-3 that you will be treated to these
warning messages.
This is what I tested in A2007 and got no warning message.
Click to expand...

Since you are not using SendObject, my earlier statement about using the
EditMessage parameter does not apply.

Earlier, you wrote: "The only versions I am looking to run are 2000, 2003,
and 2007." Without using separate physical PC's, or Virtual PC, your only
option to install multiple versions of Outlook (in order to test your code
with the same version of Outlook, to mimic a customer's setup accurately)
would be to configure separate boot drives. The reason I say this is that it
is impossible to install more than one version of Outlook on a given bootable
partition.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

Secret Squirrel said:
I've pasted some code that I am using currently in my db. This code is behind
one of my forms. When I fire this in A2000 I get no warning message from
Outlook. When I fire it in A2003 I get the warning message. I'm using "Click
Yes" to get around this in 2003. This is what I tested in A2007 and got no
warning message.

Sub SendMessageGenerateTicket(Optional AttachmentPath)
Dim objOutlook As Outlook.Application
Dim objOutlookMsg As Outlook.MailItem
Dim objOutlookRecip As Outlook.Recipient
Dim objOutlookAttach As Outlook.Attachment
Dim db As Database
Dim rsEmail As Recordset
Dim stTo, stFrom, stCC, stBCC, stSubject, stSal, stText As String
Dim stQuery As String
Dim stAttachPath As String


stSubject = "RMA#: " & Forms![2005 Form]!RMA
stText = "The Disposition for the RMA noted in the subject line has been
completed. Please generate an 'R' ticket. The original WO# is: " &
Forms![2005 Form]![WO # - Line #]

'Create the Outlook session.
Set objOutlook = CreateObject("Outlook.Application")
'Create the message.
Set objOutlookMsg = objOutlook.CreateItem(olMailItem)
With objOutlookMsg
.To = Forms![2005 Form]![GenerateTicket].Column(2)
.Subject = stSubject
.Body = stText
.Importance = olImportanceNormal ' Normal Importance
.Send
'Next

End With
Set objOutlookMsg = Nothing
Set objOutlook = Nothing

End Sub

Tom Wickerath said:
Here's one way, but I was making the assumption that you are using the
SendObject method, which may not be the case. Type "DoCmd.SendObject"
(without the quotes) into a procedure. Then select this word and press the F1
button to open context-sensitive Help. You should see the following:

The SendObject method carries out the SendObject action in Visual Basic.

expression.SendObject(ObjectType, ObjectName, OutputFormat, To, Cc, Bcc,
Subject, MessageText, EditMessage, TemplateFile)

and

EditMessage Optional Variant. Use True (–1) to open the electronic mail
application immediately with the message loaded, so the message can be
edited. Use False (0) to send the message without editing it. If you leave
this argument blank, the default (True) is assumed.

So, if you left this argument blank, you'd get True, which should result in
the message being opened in Outlook and available for you to edit (requires
you to press the Send button).


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________


:

That's a good question. Forgive my ignorance here but where would I find this
parameter? I looked in my VBA code but didn't see it.

:

Gosh, I haven't tried it yet, so I cannot say for sure. You did mention beta
version--I wonder if this annoying behavior simply was not hooked up and
working in the beta, but it is in the RTM. I simply don't know. You do have
the optional edit message parameter set to False, in order to simulate a
valid test, right?


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:

One thing I did notice with the new 2007 beta version is that when you send
an email via Outlook from Access it doesn't ask you that annoying question if
you want to allow this program to send an email. That was a pain in 2003!
Click to expand...
Click to expand...
Click to expand...
 
I think you're just a lucky guy, but, honestly, I don't remember exactly
which version + SP update caused this issue to first rear up. I think the
Outlook E-mail Security Update mentioned in this KB article was rolled into
SP-3:

http://support.microsoft.com/kb/263084

However, I note that this KB article only mentions SendObject. It includes
no mention of CreateObject, the method that you are using. Perhaps this
represents a rather incomplete implemention of Outlook security in Office
2000. Don't know.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
 
Well if it isn't broken, don't fix it. If it works this way then I'll leave
it alone, no matter which version I'm using. Thanks for the interesting
conversation this evening.

Take Care Tom
 
Hi Allen,

I used your Vista solution option1 and it was working great until today, now
every time 2003 starts it has 12.0 library. Are you aware of any new issues
with this? Option 2 does not work either.

Thanks,
Tim
 
This issue is resolved with Office 2007 SP1


Tim Reid said:
Hi Allen,

I used your Vista solution option1 and it was working great until today,
now
every time 2003 starts it has 12.0 library. Are you aware of any new
issues
with this? Option 2 does not work either.

Thanks,
Tim
Click to expand...
 
Very odd.
This is an exract from the Excel file, I downloaded with SP1, which
describes the changes:

"You install Access 2007 and Microsoft Office Access 2003 on the same
computer. When you run Access 2007 after you run Access 2003, Access 2007
takes several minutes to repair itself."

Related to this, I had to add in the 2007 Developer Extensions after each
time I opened 2003 and went back to 2007 - although this fix is not included
in the descriptions, it also seems to have been addressed after I installed
SP1. I am now moving back and forth between teh two versions without start up
delays - and gradually upgrading all my applications to 2007. Thanks to MS
for the 2007 Runtime.
 
Thanks for the info Tom. When both versions were running on my machine they
both ran a configuration routine before opening when the other was opened
previously. I removed 2007 so that I can get some work done and now it takes
10 - 15 seconds to open an empty database. Microsoft is working with me on
the problem and I will let you know what was causing my issues.
 
Back
Top