Prev: Mail database - Stevie is desperate and needs tp pimp his services
Next: Can DLookup be used to compare to a control value.
From: Steve Sanford limbim53 at yahoo dot on 5 Feb 2010 05:39
Open the query in design view. Then, in the gray area where you add the
tables, right click and select the top option "SQL View".

HTH
--
Steve S
--------------------------------
"Veni, Vidi, Velcro"
(I came; I saw; I stuck around.)


"Jennifer" wrote:

> So I am sorry to say I don't have a clue how to find the SQL of my query. I
> can look at my query in design view but how to look in SQL?
>
> I am so used to Excel all the Access language has me pulling my hair out.
> --
> Thank you,
>
> Jennifer
>
>
> "KARL DEWEY" wrote:
>
> > You have what is known as a Cartesian effect. This happens when your tables
> > are not properly joined. The quanity of records in one is multipled by the
> > number of records in the other.
> >
> > Post the SQL of your query for suggestions on how to fix.
> >
> > --
> > Build a little, test a little.
> >
> >
> > "Jennifer" wrote:
> >
> > > Hi,
> > > So new to this I could pull my hair out. So go easy on me. Thank you for any
> > > help you can offer.
> > > I have 1 query that is pulling from 3 tables. In those tables there aren't
> > > any duplicate entry's yet in the query i get duplicates for some entries. I
> > > can find no correlation as to why it could be choosing these as duplicates.
> > > Any direction?
> > > --
> > > Thank you,
> > >
> > > Jennifer
From: Fred on 9 Feb 2010 14:51
I sure that this is just a less expert way of saying what Karl already said,
but, each of your relationship lines has to have a "no duplicates" field at
one end of it. 99% of the time the "no duplicates" field is a Primary Key
field, and making it a primary key is a way to automatically prevent you from
entering duplicates.

Violating this is the most common cause of your problem.


From: KenSheridan via AccessMonster.com on 9 Feb 2010 18:48
Karl:

Those should be HAVING clauses, not WHERE clauses. The former operates after
grouping, which is what's wanted here, the latter before grouping.

Ken Sheridan
Stafford, England

KARL DEWEY wrote:
>All I can think of is to check that [Breed Description Table].Breed and
>[Exhibitor Table].[Exhibitor ID] are unique in these tables.
>An easy way is to run a query like this --
>SELECT [Breed Description Table].Breed, Count([Breed]) AS CountOfBreed
>FROM [Breed Description Table]
>GROUP BY Breed
>WHERE Count([Breed]) > 1;
>
> and
>
>SELECT [Exhibitor Table].[Exhibitor ID], Count([Exhibitor ID]) AS
>CountOfExhibitorID
>FROM [Exhibitor Table]
>GROUP BY [Exhibitor ID]
>WHERE Count([Exhibitor ID]) > 1;
>
>> Ahh gotcha. Ok so what do you need to know next?
>> SELECT [Breeding Cattle Table].[Entry No], IIf([Breeding Cattle
>[quoted text clipped - 37 lines]
>> > > > > can find no correlation as to why it could be choosing these as duplicates.
>> > > > > Any direction?

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-gettingstarted/201002/1

First  |  Prev  | 
Pages: 1 2
Prev: Mail database - Stevie is desperate and needs tp pimp his services
Next: Can DLookup be used to compare to a control value.