strategy for application upgrades

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

I am working on V1.0 of my Access application. Mgmt. wants periodic updates
as development continues. The data base currently has 13 tables, 9 of which
are lookup tables. This data is in the lookup tables is not expected to
change between versions. Of the remaining 4 tables, 1 will have significant
records added. Can anyone help me understand how I can import the data into
the new versions as they are developed?

TIA,

Rich
 
rich said:
Hello,

I am working on V1.0 of my Access application. Mgmt. wants periodic
updates
as development continues. The data base currently has 13 tables, 9 of
which
are lookup tables. This data is in the lookup tables is not expected to
change between versions. Of the remaining 4 tables, 1 will have
significant
records added. Can anyone help me understand how I can import the data
into
the new versions as they are developed?
Click to expand...

The approach is that if your working off site, or deploying updates to many
people around the world, then you need to think in terms of application
part, and a data part. (just like word has an application part, and then the
document part).

I explain this conceptual split here:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm
 
Back
Top