By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
426,122 Members | 906 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 426,122 IT Pros & Developers. It's quick & easy.

Table vs. Query

P: n/a
When building forms it better to have the source be a query or a table,
and why? I am also wondering is it better to have a few large tables,
or a lot of small tables, in regards to the number of fields. Thank you
for all of your help.

Best regards,
Coy

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Queries over tables - security reasons: usually it is advisable to not
allow users access to tables 'cuz they'll eventually try to enter the
data directly into the table or some other stupid thing. Also, queries
can be created in more restrictive/expansive ways.

Small tables - they are read faster. I've found that a properly
designed database usually produces tables with few columns.

--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQSO+z4echKqOuFEgEQInHQCdF1qauGLg/zsV6lXSWfcV9XP5+jgAnjou
VsMGQ939iAweQgmPJy0sGfRJ
=KkMe
-----END PGP SIGNATURE-----
Coy Howe wrote:
When building forms it better to have the source be a query or a table,
and why? I am also wondering is it better to have a few large tables,
or a lot of small tables, in regards to the number of fields. Thank you
for all of your help.


Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.