Re: Access General Inquiry
- From: "Allen Browne" <AllenBrowne@xxxxxxxxxxxxxx>
- Date: Mon, 24 Jul 2006 18:20:43 +0800
The best way to answer your question would be to gain some more experience
with bound forms, and see what is good about them.
Things like using the events of the form:
- Form_BeforeUpdate for record validation,
- Form_Current for responding to a record load,
- Form_BeforeInsert for complex defaults,
and the engine-level validation that takes care of fields:
- correct data types,
- indexing, validation rules,properties such as Requried,
and the use of subforms.
IMHO, you are missing most of the benefit of using Access if you don't use
bound forms most of the time.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"box2003" <spambox03@xxxxxxxxx> wrote in message
news:uRDGyKvrGHA.816@xxxxxxxxxxxxxxxxxxxxxxx
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...
.
- References:
- Access General Inquiry
- From: box2003
- Access General Inquiry
- Prev by Date: Newbie question
- Next by Date: Re: Saving a record to a different table on 'BeforeUpdate'
- Previous by thread: Access General Inquiry
- Next by thread: Newbie question
- Index(es):
Relevant Pages
|
