Only one table appears realtionwship wizard

  • Thread starter Thread starter Terry
  • Start date Start date
T

Terry

I have two tables in the same folder
the realtionship wizard onlys shows one table Access 2007
 
You are mixing terms. Tables are not in folders.
Folders are subdivisions of computer drives.
Databases reside in folders on a drive.
Tables are in databases, in folders, on a drive.
Think of fields (Database term - Access) as being the columns (Spreadsheet
term - Excel) of a table.

Are your two tables in the same database or in different databases but in
the same file folder on the drive?
 
there are two tables (HD Order and HD Lookup) both located in the same folder
path: c:\arch\access DB
Two different DB in the same folder...but shouldn't I be able to relate them
them?
 
there are two tables (HD Order and HD Lookup) both located in the same folder
path: c:\arch\access DB
Two different DB in the same folder...but shouldn't I be able to relate them
them?
Click to expand...

Don't confuse *databases* - .mdb or .accdb files - with *tables*.

A Database is a container for multiple tables, forms, reports, code and other
objects.

A Table can be related to another Table, but you can't relate one database to
another database. It's a box of stuff!

You can use File... Get External Data... Link in the menu from one database to
link to a table in a different database, or you can include both tables in the
same database.

This is a different philosophy than, say, dBase or FoxBase; what those
programs call a database is a separate Windows file (or a group of related
files). The functional equivalent in Access is one or more tables *within* a
database.
 
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?
Thanks
 
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?
Click to expand...

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
 
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
 
Thanks John,
I agree. Maybe a lookup table isn't the answer what I really want is auto
data entry
Click to expand...

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!
 
Back
Top