C
chie
How do you create a Template in Access 2003? Thanks.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
G
George
1. Unlike Access 2007, which is designed to support creation and use of a
specific "template" format for files (i.e., the .accdt format) , earlier
versions didn't have this capability.
2. In a general sense, a "template" can be anything you want it to be. For
example, you can create an mdb containing empty tables using Access 2003 and
store it for future use as a template when you want to create a similar
database in the future. That's a template of sorts. In fact, I am convinced
that there are only about ten different KINDS of tables used in every
database, so if you have those ten tables set up in a "template" database,
you can import them into any new database as a head start on creating any
new database.
specific "template" format for files (i.e., the .accdt format) , earlier
versions didn't have this capability.
2. In a general sense, a "template" can be anything you want it to be. For
example, you can create an mdb containing empty tables using Access 2003 and
store it for future use as a template when you want to create a similar
database in the future. That's a template of sorts. In fact, I am convinced
that there are only about ten different KINDS of tables used in every
database, so if you have those ten tables set up in a "template" database,
you can import them into any new database as a head start on creating any
new database.
T
Tom van Stiphout
On Thu, 1 May 2008 15:00:48 -0700, "George"
Interesting notion. Can you elaborate?
Off the cuff I'm thinking:
MainTable:
<subject>ID PK
<subject>Description UIDX
.... several other member fields
JunctionTable:
ForeignKey1 PK
ForeignKey2 PK
LookupTable:
<subject>ID PK
<subject>Description UIDX
Just trying to apply this to the Northwind or (worse) AdventureWorks
database seems to point out several failures in this thinking. But I
am keeping an open mind, and I'm very interested in what you have to
say about this subject.
-Tom.
<clip>
In fact, I am convinced that there are only about ten different KINDS
of tables used in every database
<clip>
Interesting notion. Can you elaborate?
Off the cuff I'm thinking:
MainTable:
<subject>ID PK
<subject>Description UIDX
.... several other member fields
JunctionTable:
ForeignKey1 PK
ForeignKey2 PK
LookupTable:
<subject>ID PK
<subject>Description UIDX
Just trying to apply this to the Northwind or (worse) AdventureWorks
database seems to point out several failures in this thinking. But I
am keeping an open mind, and I'm very interested in what you have to
say about this subject.
-Tom.
<clip>
In fact, I am convinced that there are only about ten different KINDS
of tables used in every database
<clip>
G
George
I've created a template accdb on the Access Templates site with these tables
in it. You can download it and take a look at what I'm thinking.
Keep in mind that I am NOT saying every table of a particular type will look
exactly alike every other table of that type. In addition to obvious
differences such as field names, there will be more or fewer fields in such
tables, depending on the business rules that govern the application.
I AM saying that I think there are fewer than a dozen different ways to
build a table (maybe a few more, maybe even a few less).
I am very interested in any feedback anyone has to offer because this
concept seems to me to be potentially quite useful.
in it. You can download it and take a look at what I'm thinking.
Keep in mind that I am NOT saying every table of a particular type will look
exactly alike every other table of that type. In addition to obvious
differences such as field names, there will be more or fewer fields in such
tables, depending on the business rules that govern the application.
I AM saying that I think there are fewer than a dozen different ways to
build a table (maybe a few more, maybe even a few less).
I am very interested in any feedback anyone has to offer because this
concept seems to me to be potentially quite useful.