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
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