B
box2003
Hello,
When I create new forms in Access, I rarely create them on a template using
a table or query as datasource. I have always set the forms up so if
necessary a query would run as the form loads, with appropriate error
checking etc... Or the form would load with empty fields, the user would do
a search, the form fields would populate, etc... Any functionality required
for the form as it relates to the table(s) is coded using either DAO or ADO
on a button click event.
I have had questions as to why I do this, as many of the databases I see
from individuals who say they program Access are mostly driven by a
datatable or query as a recordsource with wizard functionality built into
their application.
Is there a general preference for creating forms bounded to a recordsource
or unbounded? I have always preferred unbounded and then add any
functionality the user desires, additional to the basics that I would
incorporate into the form, new, edit, delete, etc...
Thanks.
When I create new forms in Access, I rarely create them on a template using
a table or query as datasource. I have always set the forms up so if
necessary a query would run as the form loads, with appropriate error
checking etc... Or the form would load with empty fields, the user would do
a search, the form fields would populate, etc... Any functionality required
for the form as it relates to the table(s) is coded using either DAO or ADO
on a button click event.
I have had questions as to why I do this, as many of the databases I see
from individuals who say they program Access are mostly driven by a
datatable or query as a recordsource with wizard functionality built into
their application.
Is there a general preference for creating forms bounded to a recordsource
or unbounded? I have always preferred unbounded and then add any
functionality the user desires, additional to the basics that I would
incorporate into the form, new, edit, delete, etc...
Thanks.