how to create an access database templeate?

  • Thread starter Thread starter kywoo
  • Start date Start date
K

kywoo

I wanna create an access database templeate(mdz file),but
i don't know how to get started. will anybody give me some
tips?

thanks a lot!
best regards,
kywoo
 
You learn something about manipulating Access' objects with VBA code, then
create the template with Forms and Code. That said, I've never seen a
template that wasn't one of the ones distributed with Access -- few people
expect to have a need to generate the same application over and over, and if
they do, it's about as easy to take an existing database, copy, and modify
than to use a template, and there's a lot of work in writing a template that
can, as Access' templates do, generate a database.

Larry Linson
Microsoft Access MVP
 
thank u,Mr.Linson!
En,I know it's a hard work now.
but it's my duty to write an access template.
is there an sample code or a technical article?

best regards,
kywoo
 
Michael (michka) Kaplan said:
An MDZ is a docfile that contains nothing but a picture and a number. The
picture shows up in the fileopen dialog if preview is showing, the number
gets sent to the database wizard.

It is in no way at all any kind of Access database.

(david)
 
There are certainly lots of examples and articles about programmatically
creating databases and database objects (try www.msdn.microsoft.com) but to
the best of my knowledge, the process of creating an MDZ-type database
wizard has never been publicly documented. You can find most of the
information that is publicly available by going to www.google.com/groups,
selecting 'advanced groups search', and searching for posts containing 'mdz'
in the title posted in the newsgroup comp.databases.ms-access where the
author is Michael Kaplan.

Even Microsoft seem to have given up on this type of database wizard. Only
ten of the twenty-plus database wizards that existed in Access 97 still
exist in later versions, and the templates available now from the Template
Gallery are not wizards that create databases programmatically, they are
simply empty, pre-created databases.

--
Brendan Reynolds (MVP)
(e-mail address removed)

thank u,Mr.Linson!
En,I know it's a hard work now.
but it's my duty to write an access template.
is there an sample code or a technical article?

best regards,
kywoo
 
"Michael (michka) Kaplan" wrote

That notwithstanding, it is possible to create a Wizard that can generate a
database. The "database wizard" to which michka refers is one that includes
wizards for generating multiple kinds of databases, but you can create a
specialized one to create one particular type. The problem is that there has
been little incentive to create such Wizards or templates, because it is far
easier and more flexible to create an empty database and let the user modify
it directly.

If kywoo is _compelled_ to write an .MDZ that works as Microsoft's MDZs do,
I fear he is Simply Out of Luck

If a Wizard will do, he/she should search for documentation on creating
Wizards (and there is some of that) for producing Controls. Then he/she
should realize that his/her Wizard will be constructed in similar fashion,
step after step. Each step may be no more complicated than a Control Wizard,
but he/she will end up with a Database Wizard that, as a whole, appears to
be complex.

If it were me, I'd start with an empty database of the kind I want, include
that inside my Wizard, and modify and export the objects to the created
database rather than trying to use all the CreateXxxxx statements to create
everything out of thin air. Unfortunately, that's about all the guidance I
have to offer.

The previously-mentioned http://msdn.microsoft.com and also
http://support.microsoft.com are good places to start looking for
information on creating Wizards.

Just as a matter of idle speculation, I wonder if kywoo is so _compelled_ to
do something that is difficult rather than something that would be a great
deal simpler because this is a school assignment. It's not that we aren't
willing to help students over stumbling blocks here; it's just that we
aren't willing to _do_ their homework because we know they won't learn
anything if we do.

Larry Linson
Microsoft Access MVP
 
Back
Top