Welcome to SPN

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

Sign Up Now!

Split Database

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

Tags:
  1. Zanstemic

    Zanstemic
    Expand Collapse
    Guest

    Based on your experience, what is the steps to updating a database that has
    been split and being used in production?

    Front End updates?

    Back End table updates?
     
  2. Loading...

    Similar Threads Forum Date
    India Team Anna splits over politics Breaking News Sep 22, 2012
    India Split in Team Anna. Two core members quit committee. Breaking News Oct 18, 2011
    Canada Community Split on Resolution Banning Non-baptized Sikhs from Running Guru Nanak Temple Breaking News Jul 14, 2011
    India High Priests May Discuss Split Gurpurabs Next Week Breaking News Jan 7, 2011
    India Split in Badal Family, Amarinder Returns to Centrestage Breaking News Dec 30, 2010

  3. Jerry Whittle

    Jerry Whittle
    Expand Collapse
    Guest

    In a perfect world, you would not release the database until it is 100%
    ready. Ha! Reality check time.

    The BE first. If you are going to be near the BE, for example not 400 miles
    from it like in one of my projects, you can make minor changes when the users
    aren't on the database. That's why a lot of DBAs work nights and weekends. If
    the database is going to be far, far away I recommend adding a few extra
    text, number, date, and even memo fields in each table. That way you won't
    have to create them when something needs to be added. If you need to make
    changes to the BE, do it first on a copy; make notes on what you did; then
    test; then make the changes in production.

    Now for the FE. I place a copy of the production FE out on the network where
    all users can get to it. I don't allow them to use it. Rather during the
    startup of their computer it is copied to the PC either through a login
    script or something in the Autoexec.bat file. This way when booting up in the
    morning, the users get the latest and greatest. Also if their FE corrupts for
    some reason, they are only a reboot away from a fix.

    Very Important! Do NOT do development using the production BE. You could
    mess up the data or really slow things down. You want to develop on a test BE
    database. For this to work you either need to work on a separate development
    network that mirrors production's drive mappings OR relink the tables to the
    production BE before putting the new FE out where it is to be copied. What
    ever you do be very, very careful not to mess with production data. Also do
    some version control; I put a version number on a label on the Switchboard
    form. Also make frequent backups of both your test and production .mdb files.
    Nothing beats a recent backup when things get strange.
    --
    Jerry Whittle
    Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


    "Zanstemic" wrote:

    > Based on your experience, what is the steps to updating a database that has
    > been split and being used in production?
    >
    > Front End updates?
    >
    > Back End table updates?
    >
    >
     
  4. John Vinson

    John Vinson
    Expand Collapse
    Guest

    On Thu, 15 Jun 2006 10:23:46 -0700, Zanstemic
    <Zanstemic@discussions.microsoft.com> wrote:

    >Based on your experience, what is the steps to updating a database that has
    >been split and being used in production?
    >
    >Front End updates?


    Delete the user's frontend database and give them the new version.
    Tony Toews' AutoFE Updater (http://www.granite.ab.ca/access.htm) is
    one good way to do so.

    >Back End table updates?


    Much harder: kick everyone out; open the backend exclusively; make the
    needed changes; distribute the new frontend using those changes; let
    folks back in.

    John W. Vinson[MVP]
     
  5. BD

    BD
    Expand Collapse
    Guest

    How to kick everyone out from the BE?

    []'s
    BD


    On Thu, 15 Jun 2006 13:39:15 -0600, John Vinson
    <jvinson@STOP_SPAM.WysardOfInfo.com> wrote:

    >On Thu, 15 Jun 2006 10:23:46 -0700, Zanstemic
    ><Zanstemic@discussions.microsoft.com> wrote:
    >
    >>Based on your experience, what is the steps to updating a database that has
    >>been split and being used in production?
    >>
    >>Front End updates?

    >
    >Delete the user's frontend database and give them the new version.
    >Tony Toews' AutoFE Updater (http://www.granite.ab.ca/access.htm) is
    >one good way to do so.
    >
    >>Back End table updates?

    >
    >Much harder: kick everyone out; open the backend exclusively; make the
    >needed changes; distribute the new frontend using those changes; let
    >folks back in.
    >
    > John W. Vinson[MVP]
     
  6. John Vinson

    John Vinson
    Expand Collapse
    Guest

  7. Jeff Conrad

    Jeff Conrad
    Expand Collapse
    Guest

    This one?

    http://home.bendbroadband.com/conradsystems/accessjunkie/kickoff.html

    <g>
    --
    Jeff Conrad
    Access Junkie - MVP
    http://home.bendbroadband.com/conradsystems/accessjunkie.html
    http://www.access.qbuilt.com/html/articles.html

    "John Vinson" wrote in message:
    news:k8f492to5d7qla6pa47toh4l5u2ldeanbr@4ax.com...

    > On Thu, 15 Jun 2006 22:31:29 +0100, BD wrote:
    >
    >>How to kick everyone out from the BE?

    >
    > Somebody has some suggestions on that, I forget who! Try Tony's site
    >
    > http://www.granite.ab.ca/access
    >
    > or one of the excellent compendia:
    >
    > http://www.mvps.org/access
    > http://home.bendbroadband.com/conradsystems/accessjunkie.html
     
  8. John Vinson

    John Vinson
    Expand Collapse
    Guest

  9. BD

    BD
    Expand Collapse
    Guest

    Thank you both.

    []'s
    BD
     

Share This Page