specified field could refer to more than one table

[sgray]

I have a query that uses two tables linked via a field called OrderNumber and it says the specified field [ordernumber] could refer to more than one table. This is what i have:

SELECT Items.Description, Items.Customer,Orders.OrderNumber,Items.PartNumber ,Items.InvoiceNumber,Orders.Supplier,Orders.DateOr dered,Orders.DateArrived


FROM Orders INNER JOIN Items ON Orders.[OrderNumber] = Items.[OrderNumber]

How do i fix this so it gets OrderNumber from the table Orders.

[Aragan]

can u explain better what do u want? my english is not perfect but i wanna help u

[sgray]

I had two tables that contained the same field name. I wanted to be able to run my query without having to change the name of one of the fields. I have ended up just changing one of the names but it would be good to know if this can still be done.

[orange]

I have a query that uses two tables linked via a field called OrderNumber and it says the specified field [ordernumber] could refer to more than one table. This is what i have:

SELECT Items.Description, Items.Customer,Orders.OrderNumber,Items.PartNumber ,Items.InvoiceNumber,Orders.Supplier,Orders.DateOr dered,Orders.DateArrived
FROM Orders INNER JOIN Items ON Orders.[OrderNumber] = Items.[OrderNumber]

How do i fix this so it gets OrderNumber from the table Orders.

Have you modified this sql since you got the error?
The error would normally occur if Access could not identify a specific field. That's why there is typically a Table.field construct to uniquely identify fields within tables. However, if the fields in the tables are named differently that Table.field construct can often be reduced to just using field names.

So, if you had all field references set up using Table.field, there should be no ambiguity, and no error.

[Aragan]

I had two tables that contained the same field name. I wanted to be able to run my query without having to change the name of one of the fields. I have ended up just changing one of the names but it would be good to know if this can still be done.

ya...if u use the Table.Field syntax u can have the same field name in different tables without problems cuz the table name will mak the difference