Never Look Data in Tables

  • Thread starter Thread starter Jill
  • Start date Start date
J

Jill

I often see lots of folks here advising never let users look at data in
tables or do not use tables as if they were spreadsheets. I would like to
hear reasons behind this advice. When I first created my Access database, I
did use the tables as if they were spreadsheets and learned some reason why I
shouldn't have. But I would like to know if there are other reasons.
Thank you.
 
If the users can get at the tables, they can delete hundreds of rows at once.
They can drop entire fields of data. They can even drop entire tables. I've
seen it done.

Also if you are using primary keys such as autonumbers, users may not
understand how the tables are joined. Heck they might not even understand the
concept of joined tables and wonder why the Orders table doesn't have the
Saleperson's information in it.
 
If you are working directly in tables or queries
== A user can delete all the records
== A user can delete multiple records
== You have limited functionality on controlling data entry
== Performance can suffer as normally you cannot easily limit the number
of records a user is working with at any one time. I have tables with 2
million records. If you open the table or a query to work in it, it
takes a LONG time to load all the records over the network.
== You can't use cascading comboboxes so a combobox can't be dependent
on other values you have entered in a record.
== You can't use listboxes
== You can't use option buttons

These are a few of the reasons. I could probably list others, but those
are enough in my opinion to justify using forms to control data entry.

OH! How about using forms and sub-forms to ensure entry of parent and
child records and make sure they are properly linked.


'====================================================
John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
'====================================================
 
Back
Top