Re: How to Distribute a New Version

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Rick Brandt (rickbrandt2_at_hotmail.com)
Date: 03/02/04 

Date: Tue, 2 Mar 2004 07:45:19 -0600

"S. Jackson" <sljack63@cox.net> wrote in message
news:BN_0c.20471$1k.2601@okepread01...
> How do you developers distribute a new improved copy of a database that
has
> already gone out to the user?
>
> I have sent out individual copies of my database across the agency for
users
> to tryout before we centralize it and begin networking it (this will be
much
> further down the road). Since then, I have made several design changes
to
> the tables and many changes to the FE and I want the users them out.
Most
> of the users are not trained and need a lot of hand-holding. Also, they
are
> spread out across the state so I do not have access to their pc's.
>
> Do I send complicated instructions for them to import all their old
tables
> into the new db, and run append queries?

What I do...

Split application so that changes to the front end are simply a matter of
replacing the file. Front end has a "first time run" routine that
establishes the links to the back end file automatically when first run.

If the new revision also involves changes to the back end file (tables),
then I will do one of two things depending on which is deemed less work or
more reliable for the circumstances.

1)
My "first time run" code described above will apply all of the changes to
the back end file. This might be the creation of new tables, or the
modification of an existing table by adding/changing a field.

2)
When the back end changes are significant I might distribute a blank
template file for the new back end and have my "first time run" routine
link to the new file and then import all of the data from the old one. 

-- 
I don't check the Email account attached
to this message.     Send instead to...
RBrandt    at       Hunter      dot      com

Relevant Pages

  • Re: How to Distribute a New Version
    ... about preserving the test data that your users have already entered. ... The agency stuck me> with doing this project even though I am a legal assistant, not a database> developer! ... > Looks like I am stuck spending hours on the phone doing it the hard way> having users import tables, do append queries to add the data to the new> tables and then deleting the old tables. ... Front end has a "first time run" routine that>> establishes the links to the back end file automatically when first run. ...
    (microsoft.public.access.gettingstarted)
  • Re: SetOption "Default Database Directory"
    ... As I said it works except for the first time the database opens and is set ... even with the rowsource problem solved. ... Database and reopen it and the form, ...
    (microsoft.public.access.formscoding)
  • Re: Storing Password
    ... allow to create their password the first time they use the program. ... file, the Registry, etc.) there's always a chance a user could delete it. ... could store the password in the database itself, ... you could save the file to a network folder for ...
    (microsoft.public.vb.general.discussion)
  • Upgrading a databse to ms access 2007? Help
    ... I have a ms access 2003 database that I would like to ... The first time I opened I had to fix a few ... I have tried to run it as a 2003 file and as a converted accdb file, ... show every thing but then the list disappears and only the first one ...
    (comp.databases.ms-access)
  • Re: Capture of First Use Date
    ... Here is another alternative done completely within the database. ... created when the main form opens. ... the first time the application is used. ... >> Where do you want to store it? ...
    (microsoft.public.access.forms)