VNU ID is Primary key in the Vendors table and it is a foreign Key in
POTerms. PO# is the primary key in Po terms. the other original tables did
not have any Primary keys. The code is included below
SELECT VENDORS.[Vendor ID], VENDORS.[VENDOR NAME], VENDORS.[Vendor ADDRESS],
VENDORS.[Vendor CITY], VENDORS.[Vendor STATE], VENDORS.[Vendor ZIP],
VENDORS.[Vendor PHONE No], VENDORS.[Vendor CONTACT], VENDORS.[Vendor EMAIL],
[PO Items].Qty*[PO Items].Price AS Total, VENDORS.[BUYER NAME],
VENDORS.[VNU-ID], [PO Terms].[PO #], [PO Terms].[PO Date], [PO Terms].[PO
Terms], [PO Terms].FOB, [PO Terms].Taxable, [PO Terms].Routing, [PO
Terms].[Plant 1], [PO Terms].[Plant 2], [PO Terms].[Plant 3], [PO
Terms].Buyer, [PO Terms].Notes, [PO Items].[Item #], [PO Items].Qty, [PO
Items].UOM, Descriptions.DESCRIPTION, [PO Terms].[Plant 4], [PO Items].Price
FROM ((VENDORS INNER JOIN [PO Terms] ON VENDORS.[VNU-ID] = [PO Terms].[VNU
ID]) INNER JOIN [PO Items] ON [PO Terms].[PO #] = [PO Items].[PO #]) INNER
JOIN Descriptions ON [PO Items].[Item #] = Descriptions.[ITEM Numb];
Jerry Whittle said:
Chances are that it's not the report. Rather it's the query driving the
report. Show us the SQL for the query. Open the query in design view. Next
go to View, SQL View and copy and past it here. Include any Information on
primary keys and relationships.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.
:
Created a report from a Query, the report has all the information, but some
of the associations are incorrect. ie. [PO#] in some cases my be with the
wrong [Vendor]. all other fields are correct. What could be causing this
error and how may I fix it. Any assistance would be greatly appreciated.
Thanks in advance
