Updates to Access design

[Ajay]

Other developers in this newsgroup will have certainly found or
developed a dependable technique to add-in updates to an installed
application.

I have the need to include changes, updates and additions to forms,
queries, and reports that are in use. Could someone please give guidance
to this newbie?

I cannot imagine the only method is to export from the old database all
the data tables and importing them back into the new version.

Thanks.
Ajay

 

[Douglas J. Steele]

Applications should be split into a front-end (containing the queries,
forms, reports, macros and modules), linked to a back-end (containing the
tables and relationships). For multi-user databases, only the back-end
should be on the server: each user should have his/her own copy of the
front-end, ideally on their hard drive. In this way, you simply replace
their front-end with the new one, and you're done. To make things even
easier, Tony Toews has a free Auto FE Updater at
http://www.granite.ab.ca/access/autofe.htm

 

[Jerry Whittle]

Doug Steele's answer is spot on.

One thing that I do besides splitting is to add a few empty columns in most
tables. Usually a Text (255), Number (Double), Date/Time, and maybe a Yes/No.
Sometimes I'll add more than one text, number, or date field if I really
don't feel comfortable about the quality of my requirements gathering or the
possibility of business rule changes.

The point is if you do have to add a column to a table, it's already there
and you don't have to mess with the BE. This is certainly a good idea when
the database is hundreds of miles away!

 

[Tony Toews [MVP]]

One thing that I do besides splitting is to add a few empty columns in most
tables. Usually a Text (255), Number (Double), Date/Time, and maybe a Yes/No.
Sometimes I'll add more than one text, number, or date field if I really
don't feel comfortable about the quality of my requirements gathering or the
possibility of business rule changes.

The point is if you do have to add a column to a table, it's already there
and you don't have to mess with the BE. This is certainly a good idea when
the database is hundreds of miles away!

I have code that checks a version number and adds the appropriate
tables, fields, indexes and relationships.

Updating an Access Backend MDBs structure using VBA code
http://www.granite.ab.ca/access/backendupdate.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

['69 Camaro]

Everyone please note that Aaron Kem.pf is attempting to impersonate one of
our regular posters again. Tom would never post such a message.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

[Tom Wickerath]

WRONG

Data and Queries should be kept ON THE DATABASE SERVER

with SQL Server you can do simple alter table statements in order to add
fields, etc