Installing updates to my app without losing the data

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have MS Access 2003 and MS Access 2003 Developer Extension and everything
else that came with Visual Studio Tools.

I have deployed a simple database application using the Package Wizard and
including Access Runtime. Now I am getting requests for changes. These
changes will probably add new tables and add fields to existing tables. And
there will certainly be new forms, queries and reports.

How can I package my revised version of this application and install it
easily without overwriting all the data that has already been entered?
 
Updating the code, forms, reports, and fixing bugs etc, and then sending
those updates is easy.

I can't imagine you gotten so far as to using the developer tools and not
yet have split you database?

Just the general development process is VERY difficult when your database is
not split. Further, your end users should get a mde for the program part.
The data part can remain a mdb...it don't matter.

So, with a split database, I often just send the client a zipped file (I
use
www.winzip.com). Or, you can even use the package wizard to include JUST
your
front end...and NOT include the runtime. This works well if you have to send
them a cd. (but, email is usually much easier).

You can read about splitting here:
http://www.granite.ab.ca/access/splitapp.htm

Now, the above solves the problem of sending update for the program part
(forms, reports, code fixes etc can all be updated with a simply file copy
this way).

however, to update the back end, that is more difficult. You either have to:

a) have the client send you the back end...you modify it..and send it
back. During this time, they can NOT add/edit data to the application.

b) write code in your startup routines to "check" the version of the
back end data file, and then if "old"version you then run some of your code
to modify the tables. In other words, you use code, or sql "ddl" commands
(alter table etc) to add new fields etc. to the back end. Writing this kind
of code can be a bit of work.
 
Back
Top