Problems with Access 2007 runtime and Office 2003

[Louverril]

I want to run my access runtime appplication on an XP machine with Access
2003 installed.

However in order to do this I have to use "open with" (or change the
shortcut target) to choose the version of access and then the system goes
through an installation procedure. If I last ran a 2003 mdb and now want to
run as accdr it "installs" runtime and if I last ran runtime it "installs"
2003.

Is there any way to avoid this installation and make the choice of
access.exe automatic. I want to run my runtime app on various platforms.

Thanks Lou

 

[Matt]

I am having no problems doing specifically what you are attempting. When you
package your database, have you tried selecting the third option requiring
the runtime files? That should work...

 

[Louverril]

I do require the runtime files - the install package installs them.

Where is your runtime installed - which folder?
Thanks Lou

 

[Matt]

Sorry for the great delay in response, our server suffered a two drive fault.
Freakin sucked. The runtime files' location on the machine that is doing
the packaging is errorneous. The installer should install them wherever they
need to be on the receiving PC, probably the Program Files directory. Try
adding the /runtime switch to the shortcut.

 

[Louverril]

Thanks Matt. Sorry to hear about your server problems. Hope it's fixed well
now.

Adding the runtime switch helps a little bit in that the correct version is
opened but still means that the system goes through its install procedure as
described above.

If your having no problems there must be something different about your
office set up? Have you got Access installed locally or via the server?

Thanks

Lou

 

[Matt]

Sorry for not catching this in your original post, but I'm pretty sure your
problem lies within using the 2007 runtime with Access 2003 on the same
machine. Yeah, that happens. It's an office thing, when you're running two
different versions of an Office product, it does go through an installation
procedure to modify some registry settings. You need to use the same version
runtime if there's a full blown copy on that machine. I realized that on the
machines that have 2003 on them here, the users are only using the databases
that I am sending them, which are all in the '07 format, so it ISN'T working
for me. Sorry! I'll try and research a little better and see what I can
come up with...

-Matt

"The only thing worse than an employee that just quits and leaves, is an
employee that quits and doesn''t leave."

 

[Louverril]

Thanks Matt for the reply. Bad news that it isn't working for you. I'm not
getting very far trying to solve it and I agree I think its changing
registry settings which make it do a partial re-install when you open the
different format.

The only chink of anything to go on I have had is that you should "install
runtime to a different location" - on one posting somewhere. Bbut I don't see
how you could do this - you get no choice on the runtime install and you
can't expect people to re-install 2003 .

If do get anywhere figuring this out please let me know.
It must be (or will be ) a common problem as people use runtime more to
avoid paying for extra 2007 licenses.

Cheers Lou

 

[Aaron_Lin]

I do require the runtime files - the install package installs them.

Where is your runtime installed - which folder?
Thanks Lou

sorry bother u ~
nice to meet u!
thanks~

 

[Aaron_Lin]

I do require the runtime files - the install package installs them.

Where is your runtime installed - which folder?
Thanks Lou

sorry~