Does anyone know of any Access 2003 books that discuss methods of updating
your application once it has been deployed to your customers, Im looking for
info like:

1) Using a cmd button, search for latest updates of the application
2) Using a cmd button, dowload latest updates

Is your database split between a front-end (FE) and backend (BE)? That's half
the battle right there.

For the FE upgrade I place a fresh copy on a network drive. As part of the
users booting up their PCs, the new FE is copied to their computer either by
a network login script or an entry in the Autoexec.bat file. Besides updating
the FE as needed, there's an added advantage of replacing a corrupt FE by
just doing a computer reboot.

Updating the BE is more of a problem especially at a remote site. Even after
hammering out the requirements and doing customer testing, things pop up. One
approach I use is to add some extra text, number, date/time, yes/no, and
maybe even a memo field to each table. That's saved my bacon a few times when
the customer forgot something and I was hundreds of miles away from the
database.
--
Jerry Whittle
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


"StuJol" wrote:

> Does anyone know of any Access 2003 books that discuss methods of updating
> your application once it has been deployed to your customers, Im looking for
> info like:
>
> 1) Using a cmd button, search for latest updates of the application
> 2) Using a cmd button, dowload latest updates
>

Go to Tony Toews's site and look for FE Updater. That will give you
the information you need to do it yourself.

HTH
--
-Larry-
--

"StuJol" <(E-Mail Removed)> wrote in message
news:586480B9-4DF4-4BDA-8453-(E-Mail Removed)...
> Does anyone know of any Access 2003 books that discuss methods of
updating
> your application once it has been deployed to your customers, Im
looking for
> info like:
>
> 1) Using a cmd button, search for latest updates of the application
> 2) Using a cmd button, dowload latest updates
>

Thanks for your reply, i have done the basics ie FE & BE etc etc.

I like the sound off adding spare fields, something i wil do but i was after
more ideas on how to update a database with respect to ckecking
for/downloading newer verions from websites.

"Jerry Whittle" wrote:

> Is your database split between a front-end (FE) and backend (BE)? That's half
> the battle right there.
>
> For the FE upgrade I place a fresh copy on a network drive. As part of the
> users booting up their PCs, the new FE is copied to their computer either by
> a network login script or an entry in the Autoexec.bat file. Besides updating
> the FE as needed, there's an added advantage of replacing a corrupt FE by
> just doing a computer reboot.
>
> Updating the BE is more of a problem especially at a remote site. Even after
> hammering out the requirements and doing customer testing, things pop up. One
> approach I use is to add some extra text, number, date/time, yes/no, and
> maybe even a memo field to each table. That's saved my bacon a few times when
> the customer forgot something and I was hundreds of miles away from the
> database.
> --
> Jerry Whittle
> Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.
>
>
> "StuJol" wrote:
>
> > Does anyone know of any Access 2003 books that discuss methods of updating
> > your application once it has been deployed to your customers, Im looking for
> > info like:
> >
> > 1) Using a cmd button, search for latest updates of the application
> > 2) Using a cmd button, dowload latest updates
> >

"Larry Daugherty" <(E-Mail Removed)> wrote:

>Go to Tony Toews's site and look for FE Updater. That will give you
>the information you need to do it yourself.

Thanks for the plug but I suspect he meant remote sites not on his
local LAN.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm