Form based on query

[john]

I created a form via the wizard with 1 main table and 2 one-on-one tables.
As i couldn't add a field to the form (a field that I added to the table
after creating the form), I googled out that the form is based on a Select
Query. I managed to alter that query so that the field shows up in the field
list.

My question is, why exactly does access base this form on a query? What is
the difference and the benefit?
Thanks,
john

[fredg]

Re: Form based on query

On Thu, 13 Jul 2006 19:16:49 +0200, john wrote:

I created a form via the wizard with 1 main table and 2 one-on-one tables.
As i couldn't add a field to the form (a field that I added to the table
after creating the form), I googled out that the form is based on a Select
Query. I managed to alter that query so that the field shows up in the field
list.
>
My question is, why exactly does access base this form on a query? What is
the difference and the benefit?
Thanks,
john

If you had based your form record source on just one table, you could
use either the table or a query based just on that one table.
But because your form record source is based on 3 tables, you must use
a query. Some multi-table queries are not updatable.
--
Fred
Please respond only to this newsgroup.
I do not reply to personal e-mail

[john]

Re: Form based on query

"fredg" <fgutkind@examp le.invalidschre ef in bericht
news:avc1rtojqp n5$.3i1eyrgp5ww $.dlg@40tude.ne t...

On Thu, 13 Jul 2006 19:16:49 +0200, john wrote:
>

>I created a form via the wizard with 1 main table and 2 one-on-one
>tables.
>As i couldn't add a field to the form (a field that I added to the table
>after creating the form), I googled out that the form is based on a
>Select
>Query. I managed to alter that query so that the field shows up in the
>field
>list.
>>
>My question is, why exactly does access base this form on a query? What
>is
>the difference and the benefit?
>Thanks,
>john

>
If you had based your form record source on just one table, you could
use either the table or a query based just on that one table.
But because your form record source is based on 3 tables, you must use
a query. Some multi-table queries are not updatable.
--
Fred

Thanks Fred. But what is the difference in behavior between basing a form on
a table and on a query. May I encounter problems in the future because of
using either one of them?
john

[fredg]

Re: Form based on query

On Thu, 13 Jul 2006 19:43:04 +0200, john wrote:

"fredg" <fgutkind@examp le.invalidschre ef in bericht
news:avc1rtojqp n5$.3i1eyrgp5ww $.dlg@40tude.ne t...

>On Thu, 13 Jul 2006 19:16:49 +0200, john wrote:
>>

>>I created a form via the wizard with 1 main table and 2 one-on-one
>>tables.
>>As i couldn't add a field to the form (a field that I added to the table
>>after creating the form), I googled out that the form is based on a
>>Select
>>Query. I managed to alter that query so that the field shows up in the
>>field
>>list.
>>>
>>My question is, why exactly does access base this form on a query? What
>>is
>>the difference and the benefit?
>>Thanks,
>>john

>>
>If you had based your form record source on just one table, you could
>use either the table or a query based just on that one table.
>But because your form record source is based on 3 tables, you must use
>a query. Some multi-table queries are not updatable.
>--
>Fred

>
Thanks Fred. But what is the difference in behavior between basing a form on
a table and on a query. May I encounter problems in the future because of
using either one of them?
john

Records in a tables are basically unordered.
Basing the form on a query, even for one table, allows you to sort and
filter the record source as you wish. Why include all of your table
fields in the form's record source if the form is only going to be
used for entering just a few field's data? And, as I stated in my
other post, you must use a query (SQL) if you need more than one table
in the form.

You won't get into 'trouble' using the table itself.
--
Fred
Please respond only to this newsgroup.
I do not reply to personal e-mail

[john]

Re: Form based on query

"fredg" <fgutkind@examp le.invalidschre ef in bericht
news:1ok6p4vmc9 2q0$.1s6iczl40z vv5$.dlg@40tude .net...

On Thu, 13 Jul 2006 19:43:04 +0200, john wrote:
>

>"fredg" <fgutkind@examp le.invalidschre ef in bericht
>news:avc1rtojq pn5$.3i1eyrgp5w w$.dlg@40tude.n et...

>>On Thu, 13 Jul 2006 19:16:49 +0200, john wrote:
>>>
>>>I created a form via the wizard with 1 main table and 2 one-on-one
>>>tables.
>>>As i couldn't add a field to the form (a field that I added to the
>>>table
>>>after creating the form), I googled out that the form is based on a
>>>Select
>>>Query. I managed to alter that query so that the field shows up in the
>>>field
>>>list.
>>>>
>>>My question is, why exactly does access base this form on a query? What
>>>is
>>>the difference and the benefit?
>>>Thanks,
>>>john
>>>
>>If you had based your form record source on just one table, you could
>>use either the table or a query based just on that one table.
>>But because your form record source is based on 3 tables, you must use
>>a query. Some multi-table queries are not updatable.
>>--
>>Fred

>>
>Thanks Fred. But what is the difference in behavior between basing a form
>on
>a table and on a query. May I encounter problems in the future because of
>using either one of them?
>john

>
Records in a tables are basically unordered.
Basing the form on a query, even for one table, allows you to sort and
filter the record source as you wish. Why include all of your table
fields in the form's record source if the form is only going to be
used for entering just a few field's data? And, as I stated in my
other post, you must use a query (SQL) if you need more than one table
in the form.
>
You won't get into 'trouble' using the table itself.
--
Fred

Thank you!
john