Best way to update database?

[Jay in PA]

Hi,

One more question while I'm here... In the application I'm writing,
the administrator will send out database updates several times a year.
The idea is for the user to import these updates, which will modify
several tables. Does anybody have any suggestions on the best way to
package these updates (Excel, XML, etc.) and have the user import
them?

Thanks to anyone who can help...

....Jay

 

[Peter Hibbs]

If you want to make changes to tables in a back-end database file then
have a look at :-
http://www.rogersaccesslibrary.com/forum/forum_posts.asp?TID=410

If you make changes to a front-end database file then you would just
give the user a later version and they would replace their current
version with the new version. You have split the database I presume!

If you need to re-link the front end to the back end at the user's
site (which you probably will) then have a look at :-
http://www.rogersaccesslibrary.com/forum/forum_posts.asp?TID=184
which can do that.

If the users are using a network and you need to replace a number of
front-end files on several computers then have a look at :-
http://www.rogersaccesslibrary.com/...?TID=409&SID=35ca7a571c89a977b2fz54fdcaecea53
which provides a utility to do that automatically.

HTH

Peter Hibbs.

 

[Fred]

Jay,

First, to help in this an many other areas, make such you application is
split into FE's and BE.

Beyond that, you are going to have to clarify what exactly you mean by
"updates" e.g.

1. Changing FE type items like queries, formreports
2. Modifying the data in the tables without replacing it in it's entireity
3. Entirely replacing data in certain or all tables
4. Modifying table structure

Hope this helps a little

 

[Jay in PA]

Hi Peter and Fred,

Thanks to both of you for your quick and helpful replies. To answer
your question, Fred, the updates will be modifying the data in the
tables--replacing some records, adding some others. There will be no
changes made to the FE stuff or the table structures.

Thanks and best wishes...

....Jay

 

[Fred]

Jay,

I think that 95% of the answer is dealing with the nature, organization and
context/datarules/metatdata which provides format/meaning to the updates.
The file format is the more trivial other 5%. Such is mostly compose of
two things:

- The information (at face value) that is in the updates
- The relation of this to existing records. (addition? Replacement?
Deletion? And in the case of replacement or deletion, how will you
specify/find/match which of the existing records is to be operated upon.