Welcome to SPN

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

Sign Up Now!

How does one update a customer's database after changes to the tab

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

  1. Beth

    Beth
    Expand Collapse
    Guest

    Is there some utility that can be included in the setup to merge old back end
    file with a new one? Every time I make a change to my ACCESS programs, I have
    to have all of my customers send me their old back end (tables) files so that
    I can manually merge their data into the new back end tables. Is this what
    all the developers do, or am I missing something?
     
  2. Loading...

    Similar Threads Forum Date
    Does Reading Baani Magically Affect Our Body And Psyche? And Does The Effect Depend On The Bani Read Intellectual Translations by SPNers Apr 30, 2016
    Does God Care What You Wear? Gurmat Vichaar Apr 23, 2016
    Hard Talk Does Amrit Erase All Sins? Hard Talk Apr 1, 2016
    What Believing In God Does To Your Brain Interfaith Dialogues Mar 26, 2016
    Interfaith I Have More Sikhs In My Cabinet Than Modi Does - Trudeau Interfaith Dialogues Mar 12, 2016

  3. Paul Overway

    Paul Overway
    Expand Collapse
    Guest

    No, not all developers do what what you're doing. ;o)

    Personally, for major updates, I create a converter utility that copies the
    old data to the new schema. You would also need some type of versioning
    info in the FE and BE though to ensure that the files are compatible. This
    way is pretty simple, and ensures the BE is up-to-date. During startup, I
    check the file version, and if it isn't what is required for the FE, I tell
    the user to run the conversion utility provided and close. For the
    converter, usually all that you'll need to do is append data from source to
    destination...in whatever table order makes sense in respect to RI. If new
    columns were added to a table, you might also need to append an appropriate
    value for that column, along with the other columns.

    An alternative would be to make the changes in the existing BE
    programatically, i.e., you could create new tables, columns, indexes, etc.
    via code. This might be fastest if there aren't many changes....and it
    isn't much trouble to implement the change from within your FE. For
    example, you'd check the file version during startup, and if it isn't up to
    date, add the table, column, or whatever.

    If you don't have many end-users, and/or the file is complex to convert,
    what you're doing might make sense (assuming it isn't something that has to
    be done constantly). In any case, all of these methods require some work on
    your part. There is no utility to include with your setup aside from
    whatever you might create for that purpose....and if it is something you
    expect end-users to run...it will need to be fairly bullet proof.

    --
    Paul Overway
    Logico Solutions, LLC
    www.logico-solutions.com


    "Beth" <Beth@discussions.microsoft.com> wrote in message
    news:887A9BED-5305-41BD-B03B-8F040048F607@microsoft.com...
    > Is there some utility that can be included in the setup to merge old back
    > end
    > file with a new one? Every time I make a change to my ACCESS programs, I
    > have
    > to have all of my customers send me their old back end (tables) files so
    > that
    > I can manually merge their data into the new back end tables. Is this what
    > all the developers do, or am I missing something?
    >
     
  4. Beth

    Beth
    Expand Collapse
    Guest

    Re: How does one update a customer's database after changes to the

    Thanks,

    I'll try to create a converter utility.

    Beth

    "Paul Overway" wrote:

    > No, not all developers do what what you're doing. ;o)
    >
    > Personally, for major updates, I create a converter utility that copies the
    > old data to the new schema. You would also need some type of versioning
    > info in the FE and BE though to ensure that the files are compatible. This
    > way is pretty simple, and ensures the BE is up-to-date. During startup, I
    > check the file version, and if it isn't what is required for the FE, I tell
    > the user to run the conversion utility provided and close. For the
    > converter, usually all that you'll need to do is append data from source to
    > destination...in whatever table order makes sense in respect to RI. If new
    > columns were added to a table, you might also need to append an appropriate
    > value for that column, along with the other columns.
    >
    > An alternative would be to make the changes in the existing BE
    > programatically, i.e., you could create new tables, columns, indexes, etc.
    > via code. This might be fastest if there aren't many changes....and it
    > isn't much trouble to implement the change from within your FE. For
    > example, you'd check the file version during startup, and if it isn't up to
    > date, add the table, column, or whatever.
    >
    > If you don't have many end-users, and/or the file is complex to convert,
    > what you're doing might make sense (assuming it isn't something that has to
    > be done constantly). In any case, all of these methods require some work on
    > your part. There is no utility to include with your setup aside from
    > whatever you might create for that purpose....and if it is something you
    > expect end-users to run...it will need to be fairly bullet proof.
    >
    > --
    > Paul Overway
    > Logico Solutions, LLC
    > www.logico-solutions.com
    >
    >
    > "Beth" <Beth@discussions.microsoft.com> wrote in message
    > news:887A9BED-5305-41BD-B03B-8F040048F607@microsoft.com...
    > > Is there some utility that can be included in the setup to merge old back
    > > end
    > > file with a new one? Every time I make a change to my ACCESS programs, I
    > > have
    > > to have all of my customers send me their old back end (tables) files so
    > > that
    > > I can manually merge their data into the new back end tables. Is this what
    > > all the developers do, or am I missing something?
    > >

    >
    >
    >
     

Share This Page