Access 2007 Runtime deployment quirks?

[PaulO]

I have recently upgraded to Access 2007 and am deploying Access Runtime 2007 split-database (program and backend files) solutions to users.



Two 'interesting' new features arise

1. When deploying just a program file upgrades (i.e. the intention being to leave the _be file intact) the user is advised that a version of the program already exists and will have to be removed using the Add/Remove Programs utility?
   • Obviously this is a real pain as the _be file would have to be backed up and restored later on!
   • Am I doing something wrong in the deployment script I have written for the upgrade?
     • I am excluding Access Runtime as of course it already exists on the user's PC but are there other things I should be including or excluding?
   • Or is there a workaround?
2. I am getting an unexpected complication when deploying two unrelated Runtime databases to the same PC. This may just be a VISTA issue?
   • The first Runtime database CD installs correctly, no problems.
   • The second Runtime database CD detects that Access Runtime 2007 is already installed and prevents installation of the database!
   • Question is, why won't VISTA simply ignore/overwrite the existing installation of Access Runtime 2007?
   • Again, is it something I'm doing wrong in the deployment script e.g. a flag not checked or set?

 

[HiTechCoach]

For the initial deployment (new install) I have two separate installs.One install of the server to place the back end . One for the work station to install only the front end. I use third installer for the runtime that can be called form the work station setup app.

You may also want to check out http://www.sagekey.com

 

[PaulO]

Many thanks for the response ... but it's not quite the issue I'm facing as the backend and program files will both be on the same PC.

 

[Rabbie]

Each User should have their own copy of the FE on their computers. There are several excellent tools available to ensure each person has the latest version.

 

[PaulO]

Hi Rabbie

Yep ... the users have the front end and back end constituents in the same directory on thier hard drive. There doesn't appear to be a problem here ...

The problem arises when a second, independant, runtime database is installed from CD into a different directory (again with a FE and BE) on the same PC. The install program seems to detect that Access Runtime 2007 is already installed and aborts the whole second installation as a result.

This problem was never encoountered with Access Runtime 2000 so I'm wondering what it is I have to do to vary the deployment and/or install programs to avoid this issue?

 

[Rabbie]

Sorry. I thought you had a more conventional setup with FE on each users PC sharing a common BE on a central server.

 

[CEH]

If the runtime is installed you do not need to install it again. It is not unique to the database. I think there is an option when compiling the DB and runtime for that. Leave off the runtime.

 

[vbaInet]

Two 'interesting' new features arise

1. When deploying just a program file upgrades (i.e. the intention being to leave the _be file intact) the user is advised that a version of the program already exists and will have to be removed using the Add/Remove Programs utility?
   • Obviously this is a real pain as the _be file would have to be backed up and restored later on!
   • Am I doing something wrong in the deployment script I have written for the upgrade?
     • I am excluding Access Runtime as of course it already exists on the user's PC but are there other things I should be including or excluding?
   • Or is there a workaround?

The db you're updating isn't an accdr is it?

1. I am getting an unexpected complication when deploying two unrelated Runtime databases to the same PC. This may just be a VISTA issue?
   • The first Runtime database CD installs correctly, no problems.
   • The second Runtime database CD detects that Access Runtime 2007 is already installed and prevents installation of the database!
   • Question is, why won't VISTA simply ignore/overwrite the existing installation of Access Runtime 2007?
   • Again, is it something I'm doing wrong in the deployment script e.g. a flag not checked or set?

Seems only one instance of the Access runtme for 2007 can be installed per machine. It would create child processes for each db that is opened or run. Install the runtime seperately from your deployment. Install your dbs then install the runtime.

 

[PaulO]

OK that seems to make sense ...

Currently I deploy the database application and Runtime 2007 on the same CD ... presumably I would then need to use two CD's (not a problem nor a cost issue)

 

[vbaInet]

.... (not a problem nor a cost issue)

With the raised VAT it might cost a bit. Phew!

 

[PaulO]

Here is what I have learned since, but additional comments welcome!

• If I require TWO separate Runtime installations, use two deployment CD's
  • One with Runtime
  • One without
  • These both install into separate directories on the C:\ drive
• However, whilst the non-Runtime application does eventually load and utilise the Runtime a warning message pops-up first, similar in nature to the 'Trusted Locations' warning you get when developing a database under the full Access licence in a foreign directory
  • This suggests that, somewhere in the Runtime deployment, a Trusted Location is set up for the first program (deployed WITH Runtime) but not for the second program?
• Question
  • How do I get BOTH folders to be Trusted Locations?

 

[vbaInet]

If you search this forum there is a registry solution to this problem (I believe).