2003 & 2007 on same machine

[Guest]

Hello,
I currently have Access 2000 & 2003 on my pc but wanted to know if I could
also run 2007 on the same machine. Is it safe to have 2 versions on one pc?

 

[Rick Brandt]

Hello,
I currently have Access 2000 & 2003 on my pc but wanted to know if I could
also run 2007 on the same machine. Is it safe to have 2 versions on one pc?

There are some irritations, but I have 5 versions installed with no
"substantial" problems.

 

[Guest]

Hi Secret Squirrel,

It depends somewhat on your operating system, especially if you need to
include Access 97 into the mix, which you didn't mention. See the following
article by Access MVP Allen Browne:

Errors using multiple versions of Access under Vista
http://allenbrowne.com/bug-17.html

One really frustrating issue that you very likely will experience is a
L-O-N-G wait when switching between versions. If your PC hardware is older,
like mine is, you might as well get up to stretch and take a coffee break if
2007 and 2003 are on the same machine. However, there is a solution to this
problem if you are willing to install additional (free) software. You can
download and install Microsoft Virtual PC for free. You then create a virtual
machine (ie. load an operating system) and load the version of Access (or
Office) that you want, plus all of the service packs. Then, you create a
second virtual machine to load the next version of Access (or Office). You
will need to check the licensing agreement for your version of Windows, as
this arrangement may require you to obtain additional licences for Windows
and/or Office. But, Virtual PC is free. It will prevent problems that can
crop up from having multiple versions of Access on one machine.


Tom Wickerath
Microsoft Access MVP

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

 

[Guest]

Thanks Rick. I'll keep my eyes open for these "irritations".

 

[Rick Brandt]

Thanks Rick. I'll keep my eyes open for these "irritations".

Mostly it affects starting a different version from the previous one (delay) and
the fact that the most recently opened version becomes the default if you
double-click an MDB file. Once you get into the habit of opening the desired
version first and then opening the desired file it's no big deal.

The delay is a PITA if you need to go back and forth a lot.

 

[Allen Browne]

You can run 2007 on the same machine as previous versions, by performing a
custom install so it leaves previous versions in place.

Every time you switch to A2007, there is a very lengthy delay (> 1 minute,
about as long a rebooting your computer) as it re-registers itself (> 10k
registry entries.) Switching back to A2003 also has a re-registry delay, but
not as long.

I am discovering that help is has beginning to disappear from previous
versions also. Pressing F1 in a keyword in the VBA screen brings up a
completely blank window (completely white execpt for title bar.) At this
stage, the help still works from the help index, but over time that
disappeared during the beta, so I'm wondering if that will be an issue also.
Perhaps it's a side effect of imperfectly written registry entries?

Have begun a list of compatibility issues here:
http://allenbrowne.com/Access2007.html#Compatibility

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

message
news:[email protected]...

 

[Guest]

Hi Tom,
Nice to hear from you. Hope all is well.
I will do some research on MS virtual PC. The only versions I am looking to
run are 2000, 2003, and 2007.
Take Care
SS

 

[Guest]

Yes, I'm fine. Thanks for asking.

One thing I forgot to mention....VPC loves (read: requires) lots of RAM
memory. You'll probably want 1 GB, minimum.


Tom Wickerath
Microsoft Access MVP

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

 

[Guest]

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!

 

[Rick Brandt]

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!

Don't really see how that is possible. The message you are describing comes
from Outlook, not from Access.

 

[Guest]

That's what I meant to say. Anyways, it's not there anymore with 2007.

 

[Guest]

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
__________________________________________

 

[Guest]

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.

 

[Rick Brandt]

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?

I just tried it. Without the option to display the outgoing message first the
warnings still come up.

 

[Jeff Conrad]

You don't receive any type of message prompt when sending these e-mails Tom. There's no way to
access any of the specific parameters either; you walk your way through a wizard and complete each
step. If you choose to manually pick the addresses, Access shows you a preview of the message where
you can make further refinements. If you choose to use e-mail addresses within the database, Access
immediately sends the messages after the wizard is complete (you don't get a preview). In either
case, you don't see any Outlook warning messages.

--
Jeff Conrad
Access Junkie - MVP
http://home.bendbroadband.com/conradsystems/accessjunkie.html
Access 2007 Info: http://www.AccessJunkie.com

in message:

 

[Guest]

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
__________________________________________

 

[Rick Brandt]

You don't receive any type of message prompt when sending these e-mails Tom.
There's no way to access any of the specific parameters either; you walk your
way through a wizard and complete each step. If you choose to manually pick
the addresses, Access shows you a preview of the message where you can make
further refinements. If you choose to use e-mail addresses within the
database, Access immediately sends the messages after the wizard is complete
(you don't get a preview). In either case, you don't see any Outlook warning
messages.

That does not sound like "automating Outlook". That sounds like a SendObject
replacement or new implementation.

 

[Guest]

Here is a sample of some code I am using to send emails from one of my forms.
When I fire this code in 2003 I get the warning message from Outlook. When I
test this in the 2007 Beta version or the 2000 version I get no warning
message from Outlook. To get around this in 2003 I've been using the "Click
Yes" freeware.

 

[Guest]

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

 

[Guest]

Hi Jeff,

Yes, I guess that makes sense if one is using a wizard to initiate the
process. I assumed that Secret Squirrel was using VBA code. Probably not a
valid assumption, but it seems like Rick Brandt just verified that the
warning still occurs in 2007. They must have come up with some method of
internally notifying Outlook that all is on the up-and-up, since the user has
to phyiscally click on buttons in the wizard screens.


Tom Wickerath
Microsoft Access MVP

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