• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 304
  • Last Modified:

Upgrading a deployed package

Hi Experts,

Apologies if this question has been asked before, however, I can't find exactly the answer I need.

I have create a split database which I have deployed using the deployment wizard.  The packaging includes the runtime and also the export to PDF addin.  All works as expected.

Now I have updated the front end and included some new reports.  

Question is, how do I now deploy the updated front end?  If I try the deployment wizard and only include the new accdr file, I get an error message telling me the application is already installed and I have to uninstall it!

Any help gratefully received.

Thanks

David
0
BigDaveStafford
Asked:
BigDaveStafford
  • 2
  • 2
1 Solution
 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
Simply send out the new version of the MDB (or MDE or ACCDB or ACCDE) ... and have customers replace the existing front end.  However, you will need to provide some sort of relinking utility to the back end.  Do you need that code?

mx

ps ... no need to apologize :-)
0
 
BigDaveStaffordAuthor Commented:
Thanks for the response.

I had thought of simply copying the new front end file (most probably an accdr file), however, I'm working on the premise that some of the users are somewhat (how to say this elegantly) inexperienced.  I really wanted to have a "here's a package - just start it and it will do the rest" solution.

As for the code to relink.  I already have that and I have assumed that if the new front end is the same name as the old front end I wouldn't need to relink anyway.  Correct?

Thanks
0
 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
"if the new front end is the same name as the old front end I wouldn't need to relink anyway.  Correct?"
Well ... *only* if ... you have some standardized folder/path resides on a customer, like
C:\YourAppFolder\YourApp.ACCDR   or whatever ... AND ... you have 'pre-linked' so to speak the FE to the BE prior to deployment.  Of course ... should the customer move the BE ... well ....!

"I really wanted to have a "here's a package - just start it and it will do the rest" solution."
Then I guess you just need some simple 'installer' that will do this ... essentially install the app to a specific predetermined location, as opposed to the full on deployment package that installs the runtime, etc.

Here is the only link I have on a free 'installer'. I cannot vouch for this per se.

mx
0
 
BigDaveStaffordAuthor Commented:
Many thanks MX.  Appreciate your help
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now