Duplicate records

[Guest]

I have constrained a table in a view that produces duplicates. Why does it
produce multiple instances, even when duplicate records do not exist. The
view properties require the table to be updatable, so aggregate or grouping
isn't feasible.
SELECT dbo.vwPipelineFileSpecific1.FILE_NUMBER,
dbo.vwPipelineFileSpecific1.FileID,
dbo.vwPipelineFileSpecific1.CLIENT_NUMBER,
dbo.vwPipelineFileSpecific1.TITLE_NUMBER,
dbo.vwPipelineFileSpecific1.LOAN_NUMBER,
dbo.vwPipelineFileSpecific1.File_TYPE_ID,
dbo.vwPipelineFileSpecific1.PARTY_ID,
dbo.vwPipelineFileSpecific1.ProductProfileID,
dbo.vwPipelineFileSpecific1.CLIENT_CONTACT_ID,
dbo.vwPipelineFileSpecific1.PROP_ADDRESS,
dbo.vwPipelineFileSpecific1.PROP_CITY, dbo.County.COUNTY AS PropertyCounty,
dbo.State.STATE AS PropertyState,
dbo.vwPipelineFileSpecific1.PROP_ZIP,
dbo.vwPipelineFileSpecific1.FILE_OPEN_DATE,
dbo.vwPipelineFileSpecific1.FILE_CLOSE_DATE,
dbo.vwPipelineFileSpecific1.TOTAL_PROJECTED_REV,
dbo.vwPipelineFileSpecific1.SELLER_OWNER_FIRST_CO_1,
dbo.vwPipelineFileSpecific1.SELLER_OWNER_MIDDLE_1,
dbo.vwPipelineFileSpecific1.SELLER_OWNER_LAST_1,
dbo.vwPipelineFileSpecific1.SELLER_OWNER_FIRST_CO_2,
dbo.vwPipelineFileSpecific1.SELLER_OWNER_MIDDLE_2,
dbo.vwPipelineFileSpecific1.SELLER_OWNER_LAST_2,
dbo.vwPipelineFileSpecific1.NOTES AS
FileSpecificNotes, dbo.Contact.CONTACT_HOTKEY, dbo.tblClient.CLIENT_HOTKEY
FROM dbo.State RIGHT OUTER JOIN
dbo.Contact RIGHT OUTER JOIN
dbo.vwPipelineFileSpecific1 LEFT OUTER JOIN
dbo.County ON dbo.vwPipelineFileSpecific1.COUNTY_ID =
dbo.County.COUNTY_ID ON
dbo.Contact.CONTACT_ID =
dbo.vwPipelineFileSpecific1.CLIENT_CONTACT_ID ON
dbo.State.STATE_ID =
dbo.vwPipelineFileSpecific1.STATE_ID LEFT OUTER JOIN
dbo.tblClient ON dbo.Contact.CLIENT_ID =
dbo.tblClient.CLIENT_ID

 

[John Vinson]

Why does it
produce multiple instances, even when duplicate records do not exist.

I presume that there are more than one record in one or more of the
linked tables which match on the linking field. This is precisely how
queries are designed to work!

Why is it necessary to have an updateable *multitable query*?
Ordinarily, if you want to update tables in a one to many
relationship, one would use a Form based on the "one" and a subform
(or subforms) based on the "many".

John W. Vinson[MVP]
Join the online Access Chats
Tuesday 11am EDT - Thursday 3:30pm EDT
http://community.compuserve.com/msdevapps