Creating an "Update" Package with Wizard

[Guest]

Access 2003. I know how to use the Package Wizard to create an installation
package for an Access database application. How can I create an Update
Package, that is a package designed to update an existing installation? If
it cannot be done with the Package Wizard, what can I use? I need to be able
to send updates to the field after the initial installation. Thanks for any
help.

 

[Douglas J. Steele]

No package should be necessary. All you do is replace the front-end database
with the new file.

 

[Guest]

Thanks Doug. That is what I am doing now. But I just wanted it to be "plug
and play" with the CD I send out, so if they don't have it installed it
installs and if they do have it installed, it checks the front end version
(or date) and then copies in the new front end if it indeed is newer than
what they have. Any thoughts on how to accomplish this?
--
Dr. Doug Pruiett
Good News Jail & Prison Ministry
www.goodnewsjail.org

No package should be necessary. All you do is replace the front-end database
with the new file.

 

[Douglas J. Steele]

It's probably simpler just to overwrite the existing file if it already
exists, rather than checking if it's necessary.

--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)

Thanks Doug. That is what I am doing now. But I just wanted it to be
"plug
and play" with the CD I send out, so if they don't have it installed it
installs and if they do have it installed, it checks the front end version
(or date) and then copies in the new front end if it indeed is newer than
what they have. Any thoughts on how to accomplish this?

 

[Alp Bekisoglu]

With all due respect to Doug and also if you think you might want to give it
a try, I use the following process in my applications for updating:
1- I have a DatabaseProperty as ProdVer which contains a string value in my
case but numeric could be easier to use
2- I also have a form again within the application which checks this
property value against the same property of the update file and enables a
"continue" button if it is newer (or higher)
3- The code behind the Continue button Shell's out to run another Access
application which copies the installed file with a _backupdate added to its
name, deletes the original and then copies the newer file to the
installation location. Then it Shell's to the installed application and
closes itself.

In my case my update file, the front-end, is on a network server and not on
a distribution CD and users' FE is configured to check the server for any
updates. I have not used the PDW of Access so can't say anything on that
part.

And topping everything; I am using Access 2000 with DAO!

Let me know if you think it can be of use to you and I will give you the
details.

Alp

 

[Douglas J. Steele]

That sounds similar to the Auto FE Updater Tony Toews has (for free) at
http://www.granite.ab.ca/access/autofe.htm

However, I had the impression that Chaplain Doug's clients weren't all
connected to the same network, so that he needed a way to do it using CDs.

--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)

With all due respect to Doug and also if you think you might want to give
it a try, I use the following process in my applications for updating:
1- I have a DatabaseProperty as ProdVer which contains a string value in
my case but numeric could be easier to use
2- I also have a form again within the application which checks this
property value against the same property of the update file and enables a
"continue" button if it is newer (or higher)
3- The code behind the Continue button Shell's out to run another Access
application which copies the installed file with a _backupdate added to
its name, deletes the original and then copies the newer file to the
installation location. Then it Shell's to the installed application and
closes itself.

In my case my update file, the front-end, is on a network server and not
on a distribution CD and users' FE is configured to check the server for
any updates. I have not used the PDW of Access so can't say anything on
that part.

And topping everything; I am using Access 2000 with DAO!

Let me know if you think it can be of use to you and I will give you the
details.

Alp

 

[Alp Bekisoglu]

Hi Doug,

Although it sound like that, I have actually took the basics from
http://www.databasejournal.com/features/msaccess/article.php/3286111
"Automatically Deploy a New Access Client By Danny Lesandrini" and did quite
a few modifications and additions to suite my needs. I don't know, maybe
because I am now very used to it, Tony's application initially seemed a bit
more complex to me.

Anyway, I thought if Chaplain Doug thinks it could give him a thing to look
into then I should flood the ng with the code.

Alp

That sounds similar to the Auto FE Updater Tony Toews has (for free) at
http://www.granite.ab.ca/access/autofe.htm

However, I had the impression that Chaplain Doug's clients weren't all
connected to the same network, so that he needed a way to do it using CDs.