How to update an application using the existing tables

  • Thread starter Thread starter OssieMac
  • Start date Start date
O

OssieMac

I have an application that I want to be able to update and then give it to
the user to install the update but the user keeps his existing tables. I have
found some limited info that indicates that I need to have the tables in a
separate file. What I am looking for is a step by step guide for what I need
to do. (I'd be surprised if what I need doesn't exist out there in cyberspace
but I just can't find what I am after.)

The following is what I think that I need:-

Separating the tables from the existing database. (I assume I just export
them.)

How to set the links between the user interface and the tables.

What sort of code do I need to provide so the user can simply click a button
to remove the links to the old version and re-establish the links to the new
version. (I am toying with the idea that all other buttons on the main menu
of the updated version will be disabled and the button to execute this will
then get hidden or removed after the links are re-established and the other
buttons re-enabled. This part I can do if I can work out how to do the above.)

As always all help will be greatly appreciated as will suggestions of other
options to achieve the desired result.
 
I have a good outline of the steps, and even how you continue to develop
here:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm
What sort of code do I need to provide so the user can simply click a
button
Click to expand...
to remove the links to the old version and re-establish the links to the new
version.

Actually, if the path names are the same, you don't need any code.

However, as a general rule, we use the code here:
http://www.mvps.org/access/tables/tbl0009.htm

And, it is your front end (program part) that links to the back end. So, in
effect, when you provide them a new program, it will overwrite the old one,
and you not have to worry about breaking links, but just setting them....
 
You could name the modified database something else and let the users import
the forms/queries/reports into their copy of the database, but the simple way
is to split your database into front end/back end. Access will do this for
you:

Tools - Database Utilities - Database Splitter

The tables will be placed in one mdb file (the back end) and everything else
into another mdb file (front end.) Then when changes in structure are needed,
you change the front end and give your users a copy of the new front end.
 
To Albert and Linq,

My thanks to you both for your replies. I think that I now have exactly what
I need and I am sure that I will now be able to complete the project.

Once again, your help is greatly appreciated.
 
Back
Top