I sorry, but I'm having problems understanding exactly what problem you're
describing.
I'll try to address what I do understand.
I'm presuming that I replace/substitute the lookup table value/
description field, e.g. ClaimSpecialistNames.ClaimSpecialistNm in
place of the C.ClaimSpecialistID so I get the individual's name
instead of the key/integer value associated w/individual's name in
table. Correct?
Assuming you've added the ClaimSpecialistNames table to your query, that's
correct.
BTW, in generating the SQL statement via concatenating field names,
e.g. strSQL = "Select a.Fld1, a.Fld2" method, I encountered that on
viewing the entire SQL statement after it failed that several field
names where split across two lines...I had to add additional spaces to
have the field name not be split. I've not run across this previously
but then have not had a query composed of so many fields.
Is there a line length limitation that I'm encountering?
Break your code into shorter lines.
strSQL = "Select a.Fld1, a.Fld2, " & _
"b.Fld1, c.Fld3, a.Fld3 " & _
"FROM a INNER JOIN b " & _
"INNER JOIN c " & _
"ON b.Fld1 = c.Fld2 " & _
"ON a.Fld1 = b.Fld2"
or
strSQL = "Select a.Fld1, a.Fld2, "
strSQL= strSQL & "b.Fld1, c.Fld3, a.Fld3 "
strSQL= strSQL & "FROM a INNER JOIN b "
strSQL= strSQL & "INNER JOIN c "
strSQL= strSQL & "ON b.Fld1 = c.Fld2 "
strSQL= strSQL & "ON a.Fld1 = b.Fld2"
[/QUOTE]
Thanks Doug for the reply.
Had previously run across the article but will reread...
Not only the form but the table fields have the lookup table fields
included. Then when I query I get the integer value not readable name.
In creating a query that includes the lookup table value not key, I'm
encountering issues...probably due to query...
I get an initial set of 5 records when not including lookup values but
after I substitute/join the first lookup table I get 3 records which
continues until I - presuming here as I have not checked on the actual
data - substitute a lookup table say WorkOutStatus then query states
that I'm about to add 0 records...
I'm presuming that I replace/substitute the lookup table value/
description field, e.g. ClaimSpecialistNames.ClaimSpecialistNm in
place of the C.ClaimSpecialistID so I get the individual's name
instead of the key/integer value associated w/individual's name in
table. Correct?
BTW, in generating the SQL statement via concatenating field names,
e.g. strSQL = "Select a.Fld1, a.Fld2" method, I encountered that on
viewing the entire SQL statement after it failed that several field
names where split across two lines...I had to add additional spaces to
have the field name not be split. I've not run across this previously
but then have not had a query composed of so many fields.
Is there a line length limitation that I'm encountering?
Thanks again for your help,
Rey
*********************************