Deployment, Version by Version

J

Jim Shaw

I'm developing an Access 2002 application with many
features. The user would like me to deploy the features I
have working now, and deploy additional features as they
become available. My concern is for the integrity of the
table data as we move from version to version of the
application.

When I install the newer version, the current data is
replaced with the test data I use.

I'm thinking about splitting the database, putting the
data tables in one database (A), and my remaining logic in
the other database (B(. Then I only need to replace
database (B) as I deploy various versions.

Is this the way it is done in the commercial world, or is
there a better way?

Thanks
 
D

david epsom dot com dot au

Jim Shaw said:
I'm developing an Access 2002 application with many
features. The user would like me to deploy the features I
have working now, and deploy additional features as they
become available. My concern is for the integrity of the
table data as we move from version to version of the
application.

When I install the newer version, the current data is
replaced with the test data I use.

I'm thinking about splitting the database, putting the
data tables in one database (A), and my remaining logic in
the other database (B(. Then I only need to replace
database (B) as I deploy various versions.

Is this the way it is done in the commercial world,
Yes

or is there a better way?

No :)

(david)
 
L

Larry Linson

If it's necessary to modify existing tables in a subsequent release, you
need to distribute code to perform the modifications, and apply it
verrrrrryyy carefully. If you're lucky, the enhancements will only require
new tables.

Alas, when a change is requested that was not part of the original plan, the
idea of "complete set of table designs" is impractical.

But then again, there are only two times in the life of a project when you
can expect changes that were not part of the original plan -- early and
often. :)

Larry Linson
Microsoft Access MVP
 
T

Tony Toews

So deployment gets interesting when a later version needs
a modified design of the underlying tables. Hummmmm?!

Best to have a complete set of table designs before first
release...smells like the old "Water Fall" development
approach.

<chuckle> Doesn't matter how much analyzing you do the client will
always want some changes.

And the waterfall approach works very well. See Ultra Frequent
Application Deployment http://www.granite.ab.ca/access/ufad.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
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top