A2007 runtime

P

Pat Hartman

I'd like to convert my current app to A2007 to make use of some of its
features but my client doesn't want to install Office 2007 yet. If I
distribute the A2007 runtime for my app, will the users run into issues when
trying to open other Access applications. Specifically, if they open my
A2007 app using the shortcut provided and then double click on an A2003
database, will that cause the A2007 runtime to open the database or the
A2003 version? I don't know all the older Access applications that they use
so I can't distribute shortcuts to avoid the "which version has control of
the registry" issue.

Also, are there any issues I need to be aware of with the installation of
the A2007 runtime when an older version of Access is already installed?

Thanks,
Pat
 
A

Arvin Meyer [MVP]

There are 2 issues with the 2007 Runtime. First it is not updated with the
Office 2007 Service Pack, so you'll need to change the way your automatic
updates work to avoid any problems. Secondly, there is the huge amount of
time (2 to 4 minutes) that it takes to switch the application in the
registry.

Other than that, It should be a piece of cake to use a shortcut which points
to the correct version, or make an entry into the SendTo Folder to allow the
different versions to be used simultaneously. I've even had both versions
(not the runtime though) open at the same time
 
P

Pat Hartman

Thanks Arvin but I cannot identify what other applications they might be
using. I can only provide a shortcut for the new one that I am
distributing. I need to know if double-clicking on an .mdb will cause the
A2007 runtime to open rather than the retail A2003 when the runtime was the
last version used.

That 2-4 minute swap time will probably be a deal breaker. The IT folks
haven't finished their testing of all the existing applications with A2007
so they really don't want to push the new version to replace A2003 for the
general population. There is also the really annoying security with A2007
that they don't want to deal with. We will probably purchase an .rtf
ActiveX control instead unless one of the softies can offer a date when the
runtime might be updated.
 
R

Rick Brandt

Pat said:
Thanks Arvin but I cannot identify what other applications they might
be using. I can only provide a shortcut for the new one that I am
distributing. I need to know if double-clicking on an .mdb will
cause the A2007 runtime to open rather than the retail A2003 when the
runtime was the last version used.

That 2-4 minute swap time will probably be a deal breaker. The IT
folks haven't finished their testing of all the existing applications
with A2007 so they really don't want to push the new version to
replace A2003 for the general population. There is also the really
annoying security with A2007 that they don't want to deal with. We
will probably purchase an .rtf ActiveX control instead unless one of
the softies can offer a date when the runtime might be updated.

It is almost never a good idea to install the Access runtime on a PC that
already has Access installed.

Does the client want these new A2007 features or do you? He is the customer so
I suggest delivering what he wants rather than what you want to give him.
 
P

Pat Hartman

Thanks for the lecture Rick. The users want a rich text control so that
text they cut and paste retains its formatting. I thought I mentioned that.
We can certainly purchase one from FMS for a lot less hassle than trying to
work with the A2007 runtime on PCs that already have retail A2003 installed.
Eventually they will convert to A2007, so I thought we'd try to go that
route rather than getting involved with 3rd party ActiveX controls which may
not work when they do finally decide to bite the bullet and convert late
next year. I went cold-turkey with the Office 2007 Beta when MS released it
to the MVPs a year and a half ago so I don't have any PCs with both versions
installed and I don't have a test PC that I can wipe and try various
installation scenarios with or I would figure this out for myself.

The "multiple versions do not play well with each other" item is a perennial
entry on my Access problems/wish list that I send to Clint and Zac every
January.

Since no one gave me an answer to my question, I will assume that the
runtime will take over and we'll go the third party control route.
Thanks,
Pat
 
G

George Nicholson

Specifically, if they open my A2007 app using the shortcut provided and
then double click on an A2003 database, will that cause the A2007 runtime
to open the database or the A2003 version?

Based on my experience with Access 2007 Retail, the answer would be yes,
unless the A2003 shortcut specifies the path to the A2003 msaccess.exe
(which you say you have no control over). Its the same "mdb file association
points to the last-opened version of msaccess.exe" issue as before except
with much longer delays when switching versions. I can't imagine that A2007
Runtime would cause this behaviour to be any different.

However, the above applies to mdbs. Not sure if the same problem would occur
if you were able to use one of the new-to-A2007 file extensions for your
app. This has just occured to me and I don't have the opportunity to test
it.
Since no one gave me an answer to my question, I will assume that the
runtime will take over and we'll go the third party control route.

Probably the safest course, as long as the project fee covers it :)
 
P

Pat Hartman

Thanks George. I had a strong suspicion that the behavior of the runtime
wouldn't be any different from the retail version behavior but hope springs
eternal.

I won't be paying for the RTF control, the client will. FMS Inc sells one
that does what we need for a reasonable price - $299 - with royalty free
distribution. Since I'm the only developer, they won't need multiple seat
licenses. I have probably wasted more than $299 in billable hours trying to
find another alternative!
 
R

Rick Brandt

Pat said:
Thanks for the lecture Rick. The users want a rich text control so
that text they cut and paste retains its formatting. I thought I
mentioned that.

The only mention of RTF was this...

I think you'd find that cutting and pasting RTF into the Access 2007 control
might not work anyway. It is actually HTML that it uses.
 
T

Tony Toews [MVP]

Pat Hartman said:
I'd like to convert my current app to A2007 to make use of some of its
features but my client doesn't want to install Office 2007 yet. If I
distribute the A2007 runtime for my app, will the users run into issues when
trying to open other Access applications. Specifically, if they open my
A2007 app using the shortcut provided and then double click on an A2003
database, will that cause the A2007 runtime to open the database or the
A2003 version? I don't know all the older Access applications that they use
so I can't distribute shortcuts to avoid the "which version has control of
the registry" issue.

Also, are there any issues I need to be aware of with the installation of
the A2007 runtime when an older version of Access is already installed?

Basically it's a PITA. If at all possible avoid multiple Access
runtimes on a system. I'm shipping an A2000 MDE with an A2003
runtime. But they only install the A2003 runtime if required. This
way my app will work with A2000 or newer runtime or retail.

If they have A97 well tough.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
P

Pat Hartman

I hear ya. It is too bad the MS doesn't understand that making multiple
versions play nicely together could actually speed the upgrade process, at
least with large corporations. If multiple versions could co-exist, they
would be more likely to role out upgrades sooner since they wouldn't have to
worry about testing/converting all existing apps prior to the roll-out.
 
T

Tony Toews [MVP]

Pat Hartman said:
I hear ya. It is too bad the MS doesn't understand that making multiple
versions play nicely together could actually speed the upgrade process, at
least with large corporations. If multiple versions could co-exist, they
would be more likely to role out upgrades sooner since they wouldn't have to
worry about testing/converting all existing apps prior to the roll-out.

It'd be some more work for MS to happily coexist the various versions.
Right now it's the file extension, MDB, MDE, etc, that invokes the
last Access version used. Which as we all know is a PITA for
multiple versions of Access.

Given the effort I've put into the Auto FE Updater to I can understand
it. There maybe be some little documented bytes in the first few or
hundred or so bytes in the MDB/MDE file that tell you what version the
MDB/MDE is. I should really play around with that when I have some
more time. Real Soon Now (TM Jerry Pournelle - Byte magazine)

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top