Deleting an .accdr FE

[AJordan]

I was trying more testing with the packaging toold that comes with the developers extension. I packaged my database and everything worked well on the computer without Access 2007.

However, when I made changes to the FE and wanted to update the deployed version. I could not overwrite, delete nor change the original FE databse. Does anyone have experience with updating a packaged .accdr FE?

 

[HiTechCoach]

I would only use the packaging tool to make the initial installation. I would NOT use it to install updates.

See:
FRONT-END AUTO-UPDATE ENABLING TOOL

Hope this helps ...

 

[AJordan]

Thanks, my only concern is that I package this and burn the DB to a CD. Once I deliver the database it's no longer on my network. So I'm really looking for something that will allow me to send an update.....I have some thoughts on this..... but maybe it's better for me to just not use the packaging tool at all

 

[HiTechCoach]

Deploying updates to an Access FE (or any software) is not a simple process. It does not matter if you are updating on the in-house LAN or at a remote site.

I use the same method for all locations lik3 this:

* desktops have a launcher app
--- checks for updates in the back end's location.
--- If found, copy the new FE
--- launch the front end from the workstation.

I use this for networks and stand alone systems.

Updates are installed by replacing the FE in the location with the back end.

For people without internet Access, I have the launcher look for updates on the CD/USB drive/Floppy.


I do not know an professional developers that actually use the packaging wizard that in in the Developer extensions for outside deployment.

Sagekey is a very popular product ( http://www.sagekey.com )

I use INNO. I have posted an example on my web site here:
Inno Installer Script (Like Sagekey)

 

[gemma-the-husky]

an accdr is a run time thnig isnt it - so you arent going to be able to modify it, perhaps - just delete and replace.

 

[HiTechCoach]

an accdr is a run time thnig isnt it - so you arent going to be able to modify it, perhaps - just delete and replace.

A .accdr is simply created by renaming an .acccdb or a .accde to .accdr. All this really does is tell Access to automatically add the /runtime command line switch when opening the database. This way it will open in runtime mode with any version of Access 2007.


If the database was an .accdb, you can simply rename the .accdr to .accdb and make changes to it.

If the database was an .accde, you can rename the .accdr to .accdb but you will NOT be able to make changes since it really is an .accde.

Hope this helps ...