Data vs. forms & Unload/reload questions

[John Smith]

A .mdb file seems to encompass both the database and all the 'code' (forms,
modules, and logic) used to CRUD the data in the tables.

1) Is there any way to separate the database from the code into separate
files, eg. the db is mydata.mdb and the 'code is in a separate file, eg.
code.mdb?

2) Say you have v1.0 of an app and the tables and attributes are populated
with data. You then go and build v2.0 of the app, adding tables and columns
to what already existed in v1.0, and perhaps moving some of the v1.0
attributes into different tables. What is the recommended way to
unload/reload data in this sort of circumstance so as to correctly get the
v1.0 data into your v2.0 database structures?


TIA

 

[Douglas J. Steele]

Actually, the recommended approach is to split the application into a
front-end (containing the queries, forms, reports, macros and modules), and
a back-end (containing just the tables). To this end, there's a Database
Splitter built into Access, although it's pretty straight-forward to do it
manually (I've never used the built-in splitter!) Tony Toews has some good
information at http://www.granite.ab.ca/access/splitapp.htm

I typically use DAO commands to add the new tables/columns to the existing
back-end in the event of making database changes with a new release, then
run whatever queries are required to do the required population. Usually
I'll do this as a separate application, rather than including it in version
2 (since it isn't required after it's been run). Tony has some comments on
this as well.