krillin said:
tnx colin, it works. I know enough to proceed with my project, i will run into some other problems but i know were to place my questions
Krillin:
You can save yourself some of those future problems by NOT putting the CompanyName directly into Table2. The reasons for this are many, including the fact that if you ever need to correct or change the name of a company, you're going to have to go through every record on Table2 and change the value in that field.
What you want to do is put the value of the PRIMARY KEY from your Companies table (Table1) into a field on Table2, which I presume is some other kind of info (such as orders). That field in Table2 is called a FOREIGN KEY. This sort of association (called a "Relationship") is what separates a Relational Database (like Access) from a "flat-file" database.
TABLE: Companies
FIELD: (Primary Key) CompanyID (TYPE: AutoNumber)
FIELD: CompanyName (TYPE: Text)
TABLE: Orders
FIELD: (Primary Key) OrderID (TYPE: AutoNumber)
FIELD: OrderedFrom (TYPE: Long Int)
Then set up a "one to many" relationship (under the Tools menu) from Companies.CompanyID to Orders.OrderedFrom.
You should really examine the sample "Northwind Traders" database, snoop through the manuals, and read some beginner-level on-line database tutorials. I don't think anyone here begrudges helping newbies (heck, they're still willing to help me...) but folks will eventually stop responding if they feel like you're just asking them to do it for you... No offense intended.
--Perpetual-Newbie Mac