db backend upgrades
in [Forms]
|
From: swas on 21 Mar 2010 20:56 Hello, I need to explore the best way to manage upgrades on a customer backend db, of which there will be many over time. My initial thought is to supply a new empty backend db, and either a) import all data from the earlier current customer db, or b) programatically step through the two db's and ensure all customer tables have the same fields and properties. Either of the above processes would be controlled by the new frontend code supplied to the customer. Being new to this level of coding, I am curious if there is a 'best practice' approach. Reading / searching for links doesn't reveal much. Thanks in advance swas
From: Tom van Stiphout on 21 Mar 2010 21:34 On Sun, 21 Mar 2010 17:56:01 -0700, swas <swas(a)discussions.microsoft.com> wrote: In a similar situation with a commercial application I did this: * Maintain a BackendVersionNumber in the back-end. * Write code in the front-end that can rev the BE from version X to version Y. * Check the BE version at startup time, and apply all changes not yet made. * Of course we're keeping backups all along. -Tom. Microsoft Access MVP > >Hello, > >I need to explore the best way to manage upgrades on a customer backend db, >of which there will be many over time. > >My initial thought is to supply a new empty backend db, and either > >a) import all data from the earlier current customer db, or >b) programatically step through the two db's and ensure all customer tables >have the same fields and properties. > >Either of the above processes would be controlled by the new frontend code >supplied to the customer. > >Being new to this level of coding, I am curious if there is a 'best >practice' approach. Reading / searching for links doesn't reveal much. > > >Thanks in advance > >swas
From: Gina Whipp on 21 Mar 2010 21:37 swas, Your code should be in your front end or are you just adding fields? Here you go... http://www.peterssoftware.com/beu.htm -- Gina Whipp 2010 Microsoft MVP (Access) "I feel I have been denied critical, need to know, information!" - Tremors II http://www.regina-whipp.com/index_files/TipList.htm "swas" <swas(a)discussions.microsoft.com> wrote in message news:D26136EE-0C3F-49FA-ADFB-529E2F66FAE1(a)microsoft.com... Hello, I need to explore the best way to manage upgrades on a customer backend db, of which there will be many over time. My initial thought is to supply a new empty backend db, and either a) import all data from the earlier current customer db, or b) programatically step through the two db's and ensure all customer tables have the same fields and properties. Either of the above processes would be controlled by the new frontend code supplied to the customer. Being new to this level of coding, I am curious if there is a 'best practice' approach. Reading / searching for links doesn't reveal much. Thanks in advance swas
From: swas on 21 Mar 2010 22:04 Gina, They are great, thanks (The link you suggested had further links also), and just what I was looking for. I assume making changes to tables (After backing up) where live data is stored is the preferred option, rather than importing all data into a new version back end. Much appreciated. swas
From: Gina Whipp on 21 Mar 2010 22:34 swas, Yes, as you really should never have to worry about the tables once created. So if you have to make additions then make a back-up, make changes and hopefully you can delete the back-ups... of course, test your changes and hold back-up for a few days just in case. Also, if you *think* you're going to have make more additions then add some extra fields... UserDefined1 UserDefined2 etc... I did that once when I had a feeling and they came in handy. Add a few text and perhaps one numeric! -- Gina Whipp 2010 Microsoft MVP (Access) "I feel I have been denied critical, need to know, information!" - Tremors II http://www.regina-whipp.com/index_files/TipList.htm "swas" <swas(a)discussions.microsoft.com> wrote in message news:E3A01543-9A60-4A2D-BDBC-98AE23F9F6DB(a)microsoft.com... Gina, They are great, thanks (The link you suggested had further links also), and just what I was looking for. I assume making changes to tables (After backing up) where live data is stored is the preferred option, rather than importing all data into a new version back end. Much appreciated. swas
|
Next
|
Last
Pages: 1 2 Prev: Combo Box autopopulate two fields in Form Next: Cancel Add Mode with Required Fields |