Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!
  1.   Become a Supporter    ::   Make a Contribution   
    Target (Recurring Monthly): $200 :: Achieved: $98

Deploying Front End and Modifications

Discussion in 'Information Technology' started by philman, Jul 28, 2006.

  1. philman

    philman
    Expand Collapse
    Guest

    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
     
  2. Loading...


  3. Rick Brandt

    Rick Brandt
    Expand Collapse
    Guest

    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
     
  4. philman

    philman
    Expand Collapse
    Guest

    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
    >
    >
    >
     
  5. Steve Schapel

    Steve Schapel
    Expand Collapse
    Guest

    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.datamanagementsolutions.biz/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.
     
Since you're here... we have a small favor to ask...

More people are visiting & reading SPN than ever but far fewer are paying to sustain it. Advertising revenues across the online media have fallen fast. So you can see why we need to ask for your help. Donating to SPN's is vote for free speech, for diversity of opinions, for the right of the people to stand up to religious bigotry. Without any affiliation to any organization, this constant struggle takes a lot of hard work to sustain as we entirely depend on the contributions of our esteemed writers/readers. We do it because we believe our perspective matters – because it might well be your perspective, too... Fund our efforts and together we can keep the world informed about the real Sikh Sikhi Sikhism. If everyone who writes or reads our content, who likes it, helps us to pay for it, our future would be much more secure. Every Contribution Matters, Contribute Generously!

    Become a Supporter      ::     Make a Contribution     



Share This Page