A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Table vs. query in forms



 
 
Thread Tools Display Modes
  #1  
Old December 8th, 2009, 06:17 PM posted to microsoft.public.access.tablesdbdesign
Jill
external usenet poster
 
Posts: 166
Default Table vs. query in forms

I've seen the practice of using queries in forms. Is this recommended? Why?

That is... I am pretty much making data entry forms and am basing them off
of the tables. Should I be making queries of these tables and basing the
forms off of these instead?

If so, should this practice include "look up tables" (tables that I'm using
in multiple combo boxes for multiple fields on the form - they just have an
ID (primary key) and a field for categories such as "0-25%", "26-50%", etc.)?

Thanks,

Jill
  #2  
Old December 8th, 2009, 06:27 PM posted to microsoft.public.access.tablesdbdesign
Lynn Trapp[_3_]
external usenet poster
 
Posts: 101
Default Table vs. query in forms

Jill,

As long as your record source for your form is a single table, then it won't
matter a lot. If you need more than one table in the record source, then you
will need to use a query.

--
Lynn Trapp


"Jill" wrote:

I've seen the practice of using queries in forms. Is this recommended? Why?

That is... I am pretty much making data entry forms and am basing them off
of the tables. Should I be making queries of these tables and basing the
forms off of these instead?

If so, should this practice include "look up tables" (tables that I'm using
in multiple combo boxes for multiple fields on the form - they just have an
ID (primary key) and a field for categories such as "0-25%", "26-50%", etc.)?

Thanks,

Jill

  #3  
Old December 8th, 2009, 07:19 PM posted to microsoft.public.access.tablesdbdesign
KARL DEWEY
external usenet poster
 
Posts: 10,767
Default Table vs. query in forms

I prefer queries as I can change and test a query without saving where as you
have to save changes to the form.
Also the query can be used for other things like a report or as source for
other queries.

--
Build a little, test a little.


"Jill" wrote:

I've seen the practice of using queries in forms. Is this recommended? Why?

That is... I am pretty much making data entry forms and am basing them off
of the tables. Should I be making queries of these tables and basing the
forms off of these instead?

If so, should this practice include "look up tables" (tables that I'm using
in multiple combo boxes for multiple fields on the form - they just have an
ID (primary key) and a field for categories such as "0-25%", "26-50%", etc.)?

Thanks,

Jill

  #4  
Old December 9th, 2009, 04:11 PM posted to microsoft.public.access.tablesdbdesign
BruceM via AccessMonster.com
external usenet poster
 
Posts: 448
Default Table vs. query in forms

I tend to use queries because they have a lot more flexibility for sorting
and filtering, and they can contain calculated fields, including doing things
such as combining first name and last name, or combining City, State, Zip
into a single line of text. There are other ways to combine fields and
perform calculations, but I usually find queries to be the most convenient.

With lookup tables it depends on what you want to display. If you are using
a combo box, with the ID field the bound column and the text the displayed
column, there is no need to include the lookup table in the form's Record
Source query, but in some cases you will want to include the table.
Sometimes when using several tables in a Record Source query you may find the
query is not updatable for one or more of several reasons.

Jill wrote:
I've seen the practice of using queries in forms. Is this recommended? Why?

That is... I am pretty much making data entry forms and am basing them off
of the tables. Should I be making queries of these tables and basing the
forms off of these instead?

If so, should this practice include "look up tables" (tables that I'm using
in multiple combo boxes for multiple fields on the form - they just have an
ID (primary key) and a field for categories such as "0-25%", "26-50%", etc.)?

Thanks,

Jill


--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...esign/200912/1

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 10:46 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.