Table Query

[Welly]

I have a database that I have inherited.

There are 3 main tables from where data is pulled. The information from
these tables has got to a point where there are a high number of duplicates
in the system as the data goes back to 2002. When running queries multiple
data is extracted from these duplicates. I am trying to reformat the tables
so that there is more than 1 field in each to link the queries.

Table 1 is my main table
Table 2 is a calculation performed on table 1
Table 3 is from a seperate source with only one matching column.

I am trying to change table 3 so that there are more columns that can be
related so that my queries will be:

WHERE A = A and B = B

making the queries more accurate.

When inserting a column with information from table 1 will I have to pull
out all the duplicate fields first so that I do not duplicate them again?

 

[Jeff Boyce]

Welly

If you are not in a position to "clean up" the duplications, consider
modifying your query to return "unique" sets of values. Open the query in
design mode, select Query | Properties, and set Unique Values to Yes.

--
Regards

Jeff Boyce
Microsoft Office/Access MVP


Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/

 

[Welly]

The problem is I need the duplicates as the numbers are reused every 18
months. This number is the only common denominator between the 3 tables.
Currently when a query is run with the duplicates you get the scenario:

1 and 1
2 and 2
1 and 2
2 and 1

creating 2 extra lines that I do not need.

 

[Jeff Boyce]

Welly

I don't understand. The 4 examples you gave are unique. Where's the
duplication?

--
Regards

Jeff Boyce
Microsoft Office/Access MVP


Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/

 

[Welly]

Sorry, The problem is that there should only be

1 and 1
2 and 2

When 1 and 2 is pulled out it is because of the duplicate value of 1 pulling
out the other data relating to 2

Hope this makes sense

 

[Jeff Boyce]

I'm not there, and I don't understand your data structure (what fields are
in what tables), and I haven't seen the SQL statement you're using.

Would it be easier to remove the duplicate records?

--
More info, please ...

Jeff Boyce
Microsoft Office/Access MVP


Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/