Prev: Create table from a crosstab query
Next: Microsoft Responds to the Evolution of Online Communities
From: John W. Vinson on 8 May 2010 00:54
On Fri, 7 May 2010 19:58:01 -0700, Terry <Terry(a)discussions.microsoft.com>
wrote:

>Yeah I figured that out from Karl's post (thanks) and was able to create the
>two tables and relate them....still having a problem with a simple lookup
>though.
>In the order table I need to look up PrtNum (part #) or by PrtNam (part name)
>and have it fill in the other fields....suggestions?

I suggest you study some of the resources below.

Tables are NOT designed for user interaction. In my opinion the Lookup Feature
was a really bad mistake on Microsoft's part, as it encourages the
inappropriate use of tables "out in the open". In a good Access (or SQL or
other relational database) application the tables are "under the hood"; users
would interact with data using Forms instead. You can have a Form based on a
table, with Subforms based on related tables, with Combo Boxes and Listboxes
based on yet other tables.

Take a look at the tutorials and at Crystal's video here.

Jeff Conrad's resources page:
http://www.accessmvp.com/JConrad/accessjunkie/resources.html

The Access Web resources page:
http://www.mvps.org/access/resources/index.html

Roger Carlson's tutorials, samples and tips:
http://www.rogersaccesslibrary.com/

A free tutorial written by Crystal:
http://allenbrowne.com/casu-22.html

A video how-to series by Crystal:
http://www.YouTube.com/user/LearnAccessByCrystal

MVP Allen Browne's tutorials:
http://allenbrowne.com/links.html#Tutorials

--

John W. Vinson [MVP]
From: Terry on 8 May 2010 13:52
Thanks John,
I agree. Maybe a lookup table isn't the answer what I really want is auto
data entry
I'll check out the links u sent. 'm starting to like Access.
Thanks again


"John W. Vinson" wrote:

> On Fri, 7 May 2010 19:58:01 -0700, Terry <Terry(a)discussions.microsoft.com>
> wrote:
>
> >Yeah I figured that out from Karl's post (thanks) and was able to create the
> >two tables and relate them....still having a problem with a simple lookup
> >though.
> >In the order table I need to look up PrtNum (part #) or by PrtNam (part name)
> >and have it fill in the other fields....suggestions?
>
> I suggest you study some of the resources below.
>
> Tables are NOT designed for user interaction. In my opinion the Lookup Feature
> was a really bad mistake on Microsoft's part, as it encourages the
> inappropriate use of tables "out in the open". In a good Access (or SQL or
> other relational database) application the tables are "under the hood"; users
> would interact with data using Forms instead. You can have a Form based on a
> table, with Subforms based on related tables, with Combo Boxes and Listboxes
> based on yet other tables.
>
> Take a look at the tutorials and at Crystal's video here.
>
> Jeff Conrad's resources page:
> http://www.accessmvp.com/JConrad/accessjunkie/resources.html
>
> The Access Web resources page:
> http://www.mvps.org/access/resources/index.html
>
> Roger Carlson's tutorials, samples and tips:
> http://www.rogersaccesslibrary.com/
>
> A free tutorial written by Crystal:
> http://allenbrowne.com/casu-22.html
>
> A video how-to series by Crystal:
> http://www.YouTube.com/user/LearnAccessByCrystal
>
> MVP Allen Browne's tutorials:
> http://allenbrowne.com/links.html#Tutorials
>
> --
>
> John W. Vinson [MVP]
> .
>
From: John W. Vinson on 8 May 2010 19:38
On Sat, 8 May 2010 10:52:01 -0700, Terry <Terry(a)discussions.microsoft.com>
wrote:

>Thanks John,
>I agree. Maybe a lookup table isn't the answer what I really want is auto
>data entry

Well, there's nothing at all wrong with *lookup tables*. They're essential,
every real database has several!

What's objectionable is *lookup fields* - using a lookup table IN a table.
It's a good tool, but it's not good to use it in that context.

You'll need to explain what you're expecting with "auto data entry". Data
should be entered once, and once only, and stored in one place, and one place
only; you would then use queries, forms with subforms, combo boxes, etc. etc.
to display that data appropriately. If you're trying to (say) have data in one
table copied into fields in another table... STOP. That's not how tables work!
--

John W. Vinson [MVP]
From: Joel Trehan on 9 May 2010 09:09


"Terry" <Terry(a)discussions.microsoft.com> a écrit dans le message de groupe
de discussion : 33862428-237D-4AC0-B481-3B40A59F0C7E(a)microsoft.com...
> I have two tables in the same folder
> the realtionship wizard onlys shows one table Access 2007
>
First  |  Prev  | 
Pages: 1 2
Prev: Create table from a crosstab query
Next: Microsoft Responds to the Evolution of Online Communities