Do you mean if you modify the table structure, and add a new field to the
table, can you have that "show" on the form? The answer is yes, and this
would course be a "developer" change..not something that your users would
ever do. However, if you add a new field (column) to the table, and your
form is based on a query, then when you bring up the form in design mode,
you will NOT see the additional fields unless you change the forms
underlying query.

So, sure, you can add new columns, but this is a "building stage" issue, and
not something that would occur during general operation of the application.
So, adding new columns is only a design issue, and we don't design software
that allows "users", or the application to add a new column. The reason for
this is then all of your reports, forms, and even code will often have to be
modified.

There are very complex accounting systems that let you assemble very complex
pricing and "assemblies" of parts etc, and these systems never require that
a new column be added to the design.

The term here is called "data modeling", and it allows you to build a
database that does not requite you to add new fields over time (or, it ones
needs to,..it should be a rare event once the application is in use).

It is also possbile that I have not understood your question...so, do feel
free to expand, or dig more more answers...

You'll have to explain what a "preset" form is. The term means nothing
to me.

                 John W. Vinson[MVP]