From: swas on 21 Mar 2010 22:44 Tom, Thanks for that. It is along these lines I was thinking, though makes me more confident to be 'ratified' thought... Regards swas "Tom van Stiphout" wrote: > 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 > > >
From: swas on 22 Mar 2010 06:41 Gina's suggested link also had a further link for another update utility by Peter Hibbs at http://www.rogersaccesslibrary.com/forum/forum_posts.asp?TID=410 I tried this and it works great. As simple as importing a few objects into the front end, using the supplied form to do changes on the developer back end, and when your front end is distributed it automatically updates the customers back end. Great. Easy. Recommended. Thanks for the input. swas
First
|
Prev
|
Pages: 1 2 Prev: Combo Box autopopulate two fields in Form Next: Cancel Add Mode with Required Fields |