How to Export "Empty Tables" +queries+forms+macros for new data base ?

[Mel]

OK, we have our Access multiple table data base designed... sorta.

The test data base was populated with fake data.

How do we export "empty tables" along with all the queries, forms,
macro's, code, etc... so we have the data base structure with no data?

If we can get here we can then import the correct beginning data into
the main table and start using the data base.

thanks for any help.

Mel

 

[Douglas J. Steele]

Take a look at the TransferDatabase method: one of the parameters is
StructureOnly.

 

[Mel]

Doug... and/or anyone

"Method" sounds like a programming thing... right?

No way to just click menu items and have a new set of empty tables...
along with the associated queries, forms, code and macro's?

If I have to code I guess we would create the code as a general
module... not attached to a particular form... right? But still in the
database loaded with the fake development data... right?

Thanks for the help.

Mel

 

[Douglas J. Steele]

If you're in the new database, you can import strictly the table definitions
from another database through File | Get External Data | Import.

Make sure you click on the "Options" button on the Import Objects dialog:
you should see a choice for "Definition and Data" or "Definition Only"

Otherwise yes, you could have a module in your development database that
uses TransferDatabase to export to another database. (For that matter, you
could have a module in your new database that uses TransferDatabase to
import from your development database)

 

[Mel]

OK... I open a new Access data base... and do as you instruct.

1 - Will that import the queries, forms, code, macro's, etc as well?

or alternate maybe...

2 - split data base so all queries, forms, code, macro's, etc are
"seperate" from the tables... then...

Do the import table definitions only thing you suggested for the new
dB... giving me the empty set of tables...

then link the 'front end' to the new back end... or import those empty
tables into the 'front end'

wadda you think?

 

[Douglas J. Steele]

In my opinion all Access applications (even single-user 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).