I'm new to this so please bare with me. I have a database on our network
that I want network clients without Access installed to be able to use. I
split the database and created an install package of the front end along with
the runtime using the developer extensions package wizard. My problem is
that anytime I make changes to forms, reports, queries, etc., I have to make
a new setup package and re-deploy all instances of the front end. Is there a
way around this? Can I automate this process for only the changed objects or
is there some other solution?
--
philman

philman wrote:
> I'm new to this so please bare with me. I have a database on our
> network that I want network clients without Access installed to be
> able to use. I split the database and created an install package of
> the front end along with the runtime using the developer extensions
> package wizard. My problem is that anytime I make changes to forms,
> reports, queries, etc., I have to make a new setup package and
> re-deploy all instances of the front end. Is there a way around
> this? Can I automate this process for only the changed objects or is
> there some other solution?

Once a user has the runtime installed all they need for updates is a new
copy of your MDE file. Tony Toews offers a free utility that makes
replacing the front end file completely automatic.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

Just ran across an earlier post on the same subject...that'll teach me to dig
a little deeper next time! Thanks for your help. I'll looking over the auto
fe updater info now.
--
philman


"Rick Brandt" wrote:

> philman wrote:
> > I'm new to this so please bare with me. I have a database on our
> > network that I want network clients without Access installed to be
> > able to use. I split the database and created an install package of
> > the front end along with the runtime using the developer extensions
> > package wizard. My problem is that anytime I make changes to forms,
> > reports, queries, etc., I have to make a new setup package and
> > re-deploy all instances of the front end. Is there a way around
> > this? Can I automate this process for only the changed objects or is
> > there some other solution?
>
> Once a user has the runtime installed all they need for updates is a new
> copy of your MDE file. Tony Toews offers a free utility that makes
> replacing the front end file completely automatic.
>
> --
> Rick Brandt, Microsoft Access MVP
> Email (as appropriate) to...
> RBrandt at Hunter dot com
>
>
>

Philman,

Tony's utility is great. However, if your scenario doesn't require that
level of power, you may be interested in this idea...
http://accesstips.datamanagementsolu...z/versions.htm

--
Steve Schapel, Microsoft Access MVP

philman wrote:
> Just ran across an earlier post on the same subject...that'll teach me to dig
> a little deeper next time! Thanks for your help. I'll looking over the auto
> fe updater info now.