Re: Non-Equal values in Queries
- From: Bob <Bob@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 13 Feb 2006 06:48:27 -0800
If I am missing something ( and I probably am ) forgive me. I believe what
you state below still does not give me the employee info and the state that
they do not have a license in. It may give me the employee infor, but not
the state. I keep thinking I need some reference whos results are not equal
to the existing license.
"Jeff Boyce" wrote:
So, you're saying that the Employee (table) info and the state(s) in which.
the employee can practice are related via the AdjInit fields in each.
Sounds like a query that returns Employee info and all state(s) info. If
there's a chance you have an Employee without any states, you'd want to
change the join to be directional. Hightlight the join, change the
properties to include all (qualifying) rows from Employee and any (matching)
rows from your Cognos table.
Next, it looks like your Employees could have 0-to-many records in the
Employee Training table. That sounds like the "state" situation. You could
open the query (from above) in design mode and add the Training table, again
joining to include all employees and any training record info.
--
Regards
Jeff Boyce
Microsoft Office/Access MVP
Microsoft IT Academy Program Mentor
"Bob" <Bob@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:24898809-BFAE-4780-A6FB-5AC9F059EC13@xxxxxxxxxxxxxxxx
The AdjInit field is what I use. That way I don't have to rely onaccurate
spelling. AdjInit in each table is unique to that individual, thoughthere
are many records for each Adjinit.to
"Jeff Boyce" wrote:
Bob
It doesn't appear as if you have a (?reliable) way to connect employees
quiteyour "Cognos Data". While you have a name-like field in both, are you
sameconfident that "Bob Smith" in one table is not "Robert J. Smith" in the
other? If you are assured that both record the same person name the
thanway in both, you are still in trouble, as your system could have more
inone "Robert Smith". Without an absolutely guaranteed unique identifier
EmpIDtwo table you wish to join, you can't.
--
Regards
Jeff Boyce
Microsoft Office/Access MVP
Microsoft IT Academy Program Mentor
"Bob" <Bob@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9B0713C6-6479-4C51-BB6F-BF776BA3E009@xxxxxxxxxxxxxxxx
I have an Employee Info Table that holds the employee information,
training(pri
key, txt), BCO (#), EmpName(Txt), AdjInt(Txt), DOH(date), CurPos(Txt)
CurPosStrtDte(date), PrevPost(Txt), IndExp(Txt), and YearsExp(#). +
Then I have an Emp Training Table that collects the individuals
License#(Txt),LicExpDate(Date).history EmpID(Txt), Type(Txt), State(Txt),
whatNo primary key defined as unique values are not guaranteed.
Finally I get a feed from our system that indicates who is handling
State(Txt).in
what state called Cognos Data AdjName(Txt), AdjInit(Txt) and
license
The goal is to write a query that will indicate for me who is handling
business in a state where they either do not have a license or their
has expired.
- Follow-Ups:
- Re: Non-Equal values in Queries
- From: Jeff Boyce
- Re: Non-Equal values in Queries
- References:
- Re: Non-Equal values in Queries
- From: Jeff Boyce
- Re: Non-Equal values in Queries
- From: Bob
- Re: Non-Equal values in Queries
- From: Jeff Boyce
- Re: Non-Equal values in Queries
- Prev by Date: Re: Numering records in a group
- Next by Date: Re: Create query from list in a table
- Previous by thread: Re: Non-Equal values in Queries
- Next by thread: Re: Non-Equal values in Queries
- Index(es):
Relevant Pages
|