Access 2007 Runtime on Machine With Older Version?

[Neil]

A client of mine likes some of the new bells and whistles in Access 2007,
and is thinking about converting our A03 format MDB to an A07 format file.
However, while some of the users have A07, many do not, and it's not clear
when they would get it. His thought was to use the upcoming Access 2007
runtime to allow the users who are still running Office 2003 to be able to
run the database.

While I use multiple versions of Access on my development machine, I advised
him against this, as I recall from years ago with the Access 97 runtime that
it caused problems when run on a machine that had an older version of Access
installed. But it's been a while since I've used the Access runtime.

And, while the Access 2007 runtime isn't out yet, so it's hard to comment on
it, many here may have used the runtime version of Access after Access 97,
which is the last one I used. So I thought I'd ask for peoples' opinions
about this situation. Do you think it's wise to use the upcoming A07 runtime
on a machine that has Office 2003 installed, so the user can use an A07
database?

Thanks!

 

[Tony Toews [MVP]]

A client of mine likes some of the new bells and whistles in Access 2007,
and is thinking about converting our A03 format MDB to an A07 format file.
However, while some of the users have A07, many do not, and it's not clear
when they would get it. His thought was to use the upcoming Access 2007
runtime to allow the users who are still running Office 2003 to be able to
run the database.

While I use multiple versions of Access on my development machine, I advised
him against this, as I recall from years ago with the Access 97 runtime that
it caused problems when run on a machine that had an older version of Access
installed. But it's been a while since I've used the Access runtime.

And, while the Access 2007 runtime isn't out yet, so it's hard to comment on
it, many here may have used the runtime version of Access after Access 97,
which is the last one I used. So I thought I'd ask for peoples' opinions
about this situation. Do you think it's wise to use the upcoming A07 runtime
on a machine that has Office 2003 installed, so the user can use an A07
database?

Using A2007 runtime on a system without any version of Access
installed should be fine.

Installing multiple versions of Access, runtime or full version, can
be highly irritating to users who don't know what is going on.
Especially when they can't run an important app because an older
version of Access is attempting to open a newer version of an Access
MDB/MDE. This is due to Access changing the MDB/MDE/etc extension
association to the last version of Access which was executed.

However if you know the magic incantations all can be made well. I'm
running A97, A2000, A2002, A2003 and A2007 on my system.

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/

 

[Neil]

Thanks, Tony. Yeah, I too have several versions of Access running. And I
agree about the association issue. But I seem to recall, back from the 97
runtime, that installing the runtime with an existing version of Access
would overwrite certain files and cause the full version of Access that had
already been installed to not function properly. But maybe that was just
rumor and speculation.

 

[Guest]

Yes, they constantly re-install themselves if you are using multiple
versions. And if you don't have sufficient permissions, or if the
install files are not cached correctly, the re-installation fails, and
you can't use your application anymore. Painful if it's a business
critical application.

And more often a problem if one of the versions is A97 (requires
more permissions), or on Vista (requires more permissions).

(david)

 

[Neil]

Thanks.

Yes, they constantly re-install themselves if you are using multiple
versions. And if you don't have sufficient permissions, or if the
install files are not cached correctly, the re-installation fails, and
you can't use your application anymore. Painful if it's a business
critical application.

And more often a problem if one of the versions is A97 (requires
more permissions), or on Vista (requires more permissions).

(david)

 

[Yvonne Anderson]

What it is this group, and why is it appearing on my computer?

Yvonne Michele Anderson
(e-mail address removed)

 

[Larry Linson]

Already answered, Yvonne. Check the other times you asked the identical
question, then go to your newsreader software and unsubscribe.

Larry Linson
Microsoft Access MVP

 

[A a r o n K e m p f]

you need A c c e s s D a t a P r o j e c t s

 

[Neil]

Really? Why is that? Apart from the fact that ADPs have been frowned upon
for years by developers, and now even Microsoft is discouraging their use,
what possible connection could there be between ADPs and having mixed
versions of Access by using the Access 2007 runtime?

 

[.]

Yes, they constantly re-install themselves if you are using multiple
versions. And if you don't have sufficient permissions, or if the
install files are not cached correctly, the re-installation fails, and
you can't use your application anymore. Painful if it's a business
critical application.

And more often a problem if one of the versions is A97 (requires
more permissions), or on Vista (requires more permissions).

(david)







- Show quoted text -

We unfortunately have multiple versions of Access running, including
Access 97. My system was recently upgraded to Office 2007. Now,
whenever I open an Access 97 db and subsequently open another db using
Access 2007, the software goes through a two minute configuration/
setup routine. The installing tech acknowledged this issue and said
they had a registry hack that prevented the problem with Access 97 and
Access 2000 but as of yet have no solution for the 97/2007 problem.
So, does anyone out there have the fix?

 

[Tony Toews [MVP]]

We unfortunately have multiple versions of Access running, including
Access 97. My system was recently upgraded to Office 2007. Now,
whenever I open an Access 97 db and subsequently open another db using
Access 2007, the software goes through a two minute configuration/
setup routine. The installing tech acknowledged this issue and said
they had a registry hack that prevented the problem with Access 97 and
Access 2000 but as of yet have no solution for the 97/2007 problem.
So, does anyone out there have the fix?

There is no solution to this problem yet that I'm aware of. As soon as there is one
we'll post to the newsgroups.

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/

 

[Chris Mills]

Please be aware that, according to "Camaro 69" "Gunny", Aaron Kemph has been
accused (hundreds of times) by Gunny of impersonating the MVP Tom Wickerath.
Though apparently not in this case.

Regardless, Aaron seems to have a fetish about ADP. Since that is also a
Microsoft product, only the most foolish would imagine it solves all problems!

My own belief, if you restrict the reply to MS-Access and runtime, is that it
is better to distribute a certain version of Access (in my case A2000, and
Runtime if needed), regardless of what else is on the machine. Access is
generally reported to run well with multiple versions installed (which is
different from denying the odd problem).

In any case, if a program is written to be compatible with (say, A2000), it is
unlikely to take advantage of new features in (say, A2007).

My position, and I dont have experience of A2007 yet, is that I continue to
run and install an A2000 program under A2000 runtime regardless of whether
they have A2002 or A2003. Since there is no advantage to be gained from a
later version Access, assuming my prog is A2000, (and assuming no
compatibility issues rear their ugly heads), why the x would I want to run it
under A2007? Multiple Access versions seems the lesser evil, and every report
says that's OK. OTOH, at times I have verified that my prog runs OK on later
Access, so if they insist on later Access with the same prog, then do your own
tests to see if it runs OK or whether it strikes problems or not. Regardless
of any advice, only YOU can test the likelihood of success running YOUR prog
under A2007. I will take my normal course of demonstrating my prog works in
A2000, and any other issues are customer PC (or Microsoft) incompatibilities!

I have by no means finished with this statement! My approach has worked in a
commercial environment so far. That's an environment where I have little
control over what else they have, of course.

Chris

 

[Neil]

Please be aware that, according to "Camaro 69" "Gunny", Aaron Kemph has
been
accused (hundreds of times) by Gunny of impersonating the MVP Tom
Wickerath.
Though apparently not in this case.

Regardless, Aaron seems to have a fetish about ADP. Since that is also a
Microsoft product, only the most foolish would imagine it solves all
problems!

Here's my theory: he's invested time in developing ADPs, and now MS is no
longer promoting them or developing ADO any further. So he feels that if he
can get enough people to use ADPs through his "campaign" that he'll create a
groundswell of support, and MS will have to keep the technology alive.

My own belief, if you restrict the reply to MS-Access and runtime, is that
it
is better to distribute a certain version of Access (in my case A2000, and
Runtime if needed), regardless of what else is on the machine. Access is
generally reported to run well with multiple versions installed (which is
different from denying the odd problem).

In any case, if a program is written to be compatible with (say, A2000),
it is
unlikely to take advantage of new features in (say, A2007).

Right. In our case, though, it was the other way around. The client wants to
take advantage of the new features in Access 2007, and, so, port the program
to Access 2007 format. That's fine for users who have Access 2007, or who
don't have Access at all (but who could use the A07 runtime). But users who
have a previous version of Access would have to install the A07 runtime in
addition to their current version.

My position, and I dont have experience of A2007 yet, is that I continue
to
run and install an A2000 program under A2000 runtime regardless of whether
they have A2002 or A2003. Since there is no advantage to be gained from a
later version Access, assuming my prog is A2000, (and assuming no
compatibility issues rear their ugly heads), why the x would I want to run
it
under A2007? Multiple Access versions seems the lesser evil, and every
report
says that's OK. OTOH, at times I have verified that my prog runs OK on
later
Access, so if they insist on later Access with the same prog, then do your
own
tests to see if it runs OK or whether it strikes problems or not.
Regardless
of any advice, only YOU can test the likelihood of success running YOUR
prog
under A2007. I will take my normal course of demonstrating my prog works
in
A2000, and any other issues are customer PC (or Microsoft)
incompatibilities!

Well, as stated above, I think the reason for my post was different from
what you thought. But, regarding incompatibilities, there are issues when
running an A2K program under A07. Mostly it's just in things where Access
acts a different way. For example, in my A2K program, there's a piece of
code where the user select an option button and a subform is requeried
according to that option. In A2K, the program uses the default value of the
option button and filters the subform automatically. When the same code is
run in A07, I have to explicitly call the option button's AfterUpdate event
in the Form Current event, in order to get the subform to be filtered.

So, little things like that creep up when running an A2K database under A07,
but nothing major. This, by the way, is similar to what happened with A97
databases run under the (then-new) A2K (even after it was convered to A2K
format), but not from A2K to A02 or A03. So whenever there's a major upgrade
(A97; A2K; A07) there are going to be incompatibilities when running
databases created under prior versions.

Anyway, thanks for your note.

Neil

 

[DAVID]

You should start by replacing MSACCESS.srg with an
empty file.

MSACCESS.srg is the self-registration file for
A97. By removing the contents of this file, you
make A97 start faster, and remove some of the
permission problems when A97 attempts to self
register.

Also, by preventing A97 from re-registering, you
reduce the number of changes A2007 finds in the
registry when it starts.

With A2007, you can trace through the registery
for all of the A2007 objects, and remove the
LocalServer\LocalServer entries (leaving the
LocalServer\Default entries).
The LocalServer\LocalServer entries point to
the install cache somehow, and are used to
check and correct the registry. If you remove
them, I expect that the com subsystem will
just use the \default entry: that worked for
2003, I don't know about 2007.

(david)

 

[Tom Wickernards]

I would reccomend 'Keep it simple stupid'

there are no features in Access 2007 that make this config worthwhile

 

[Tom Wickernards]

ADPs have not been frowned upon for years

they have been frowned upon BY ONE HANDICAPPED DORK NAMED KAPLAN


ADP kick butt buddy; im so sorry that you think that MDB is sooooo much
better


but you don't understand; I feel bad for you


do you realize that I can spend twice as much time developing as you can?
do you realized that I specialized in SQL Server, meanwhile you MDB script
kids are still making $12/hour?

Screw you and screw jet buddy

SQL Server is extremely popular

 

[Tom Wickernards]

SINCE THERE IS NO ADVANTAGE TO BE GAINED FROM A LATER ACCESS VERSION?

YOU OBVIOUSLY MY FRIEND, KNOW NOTHING ABOUT ADP

 

[Tom Wickernards]

wow.. someone finally caught a clue!

and the FACT that I deal with 100 people that constantly spread
mis-information about ADP
so yeah of course I'm going to stand up for my platform of choice

 

[Guest]

After searching my C: drive (including hidden and system files), I could not
find msaccess.srg or wizard.srg. I used Notepad to create two empty files,
but I still end up with the same problem. Access 2007 goes through a setup
process if I have opened an older version of Access. Any suggestions? I am
not comfortable editing the registry.

 

[Guest]

Access 97 will not start without msaccess.srg. If you do not
have msaccess.srg, you are not using Access 97, or, you have
not found it yet.

msaccess.srg is only relevant to Access97. No other version
of access uses msaccess.srg. All newer versions use a different
installation process, and all older versions did not have registry
installation. (except for A95, which should not be used at all)

If you have Access 97 and a newer version on the same PC,
you can get around some of the problem by emptying out the
msaccess.srg, which directly alters the A97 start up process,
and indirectly alters the startup process for other versions after
A97 has run.

If you have not found msaccess.srg, you are not using A97,
or you have not found it yet.

(david)