Some text isn't recognized in report's query

[JimTrekker via AccessMonster.com]

I am using a parameter query to gather specific text data from a table to
show in a report, and I know the text is in the table. If I request one
string of text (such as "6AB42"), I get a report with all the records
containing that string. If I ask for another string (like "8WH2"), a blank
report will appear with #Error in all the fields, even though I've verified
that each string I entered is in the table in several records. I'm still a
novice at Access, and I didn't create this database, so I could really use
some help to tell me why this query-to-report will see some text and ignore
other text.

 

[tina]

please don't multi-post. for more information, see
http://home.att.net/~california.db/tips.html#aTip10.

hth

 

[JimTrekker via AccessMonster.com]

Gee, thanks, Tina. This is the first newsgroup I've ever joined (a couple of
days ago, in fact), and this was the first posting I've ever made to one
(naturally) with a specific question I'd like to have answered. Since it
related to both queries and reports, and because I didn't know of any
prohibitions, I put my question in both categories. Tonight, I got back in
to check, hoping someone had a fix for my problem, and I was excited when I
saw there was a reply! Did someone provide a great answer for me? NO, it
was only the protocol police griping at me for doing something I didn't even
know was frowned upon. What an excellent way to welcome in a new member -
Way To Go! OK, now that I've learned my lesson (notice that I didn't post
this reply in both places!), could you please be more helpful by pointing me
in a direction that will answer my question?

please don't multi-post. for more information, see
http://home.att.net/~california.db/tips.html#aTip10.

hth

I am using a parameter query to gather specific text data from a table to
show in a report, and I know the text is in the table. If I request one

[quoted text clipped - 5 lines]

some help to tell me why this query-to-report will see some text and ignore
other text.

 

[John Spencer]

Ok, from what you are saying, it appears that the report is fine.
Something about the query is failing.

What is the exact query you are using? (View the query in SQL text mode
and post the SQL text).

Is more than one table involved?

Is it possible that "8WH2" is the total content of the field and that
"6AB42" is not the total content of the field but has other characters
in the field (leading spaces, etc.)?

Try using criteria with the Like operator and wildcard characters to see
if that works.
Like "*6AB42*"

If that does return your expected records (and perhaps others you don't
want) then try
Like "*6AB42"
to see if there is a leading character that you are not seeing. You can try
Like "6AB42*"
to check and see if there are trailing invisible-to-the-human-eye
characters.



'====================================================
John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
'====================================================

 

[tina]

i posted a polite request, with a link to a webpage that explains the
reasons *why* multi-posting is frowned on in these newsgroups - because i
assume when somebody does multi-post it's because they don't know any
better, not because they're being pigheaded. i don't normally waste time on
rude, sarcastic post-ers, so no i won't be able to help you, Jim. but
perhaps MVP John Spencer in this thread, or MVP Ken Snell in the other
thread, will be able to help you. and hopefully they'll both see that
they've given you essentially the same answer, and won't waste more of their
valuable time duplicating each others' efforts.

Gee, thanks, Tina. This is the first newsgroup I've ever joined (a couple of
days ago, in fact), and this was the first posting I've ever made to one
(naturally) with a specific question I'd like to have answered. Since it
related to both queries and reports, and because I didn't know of any
prohibitions, I put my question in both categories. Tonight, I got back in
to check, hoping someone had a fix for my problem, and I was excited when I
saw there was a reply! Did someone provide a great answer for me? NO, it
was only the protocol police griping at me for doing something I didn't even
know was frowned upon. What an excellent way to welcome in a new member -
Way To Go! OK, now that I've learned my lesson (notice that I didn't post
this reply in both places!), could you please be more helpful by pointing me
in a direction that will answer my question?

please don't multi-post. for more information, see
http://home.att.net/~california.db/tips.html#aTip10.

hth

I am using a parameter query to gather specific text data from a table to
show in a report, and I know the text is in the table. If I request

one
[quoted text clipped - 5 lines]

some help to tell me why this query-to-report will see some text and ignore
other text.

 

[JimTrekker via AccessMonster.com]

OK, here’s the complete SQL statement (thanks for telling me how to get it –
as I mentioned, I’m still pretty inexperienced but trying to learn):

SELECT t_Busrows.BUSROW, t_Busrows.CIRCUIT, t_Busrows.PANEL, t_Busrows.PnlLoc,
t_Busrows.MFG, t_Busrows.TRIP, t_PowerBoxInfo.BoxLocation, t_PowerSystemInfo.
CompmentItem, t_PowerEquipStandard.Mean_Amps, t_PowerSystemInfo.
ComponentPhaseA, t_PowerSystemInfo.ComponentPhaseB, t_PowerSystemInfo.
ComponentPhaseC, ([Mean_Amps]*[ComponentPhaseA])/100 AS PhaseALoad, (
[Mean_Amps]*[ComponentPhaseB])/100 AS PhaseBLoad, ([Mean_Amps]*
[ComponentPhaseC])/100 AS PhaseCLoad, t_PowerEquipStandard.Manufacture,
t_PowerEquipStandard.Description, t_PowerSystemInfo.SystemNumber,
t_PowerSystemInfo.SystemComponentAlpha, t_PowerSystemInfo.SystemName,
t_PowerSystemInfo.DualPower, t_Busrows.mAMPA, t_Busrows.mAMPB, t_Busrows.
mAMPC, t_Busrows.mDATE
FROM t_PowerEquipStandard INNER JOIN (t_PowerSystemInfo INNER JOIN
(t_PowerBoxInfo INNER JOIN t_Busrows ON t_PowerBoxInfo.BoxBussConnect =
t_Busrows.BUSROW) ON t_PowerSystemInfo.SystemBoxLocation = t_PowerBoxInfo.
BoxLocation) ON t_PowerEquipStandard.Model_Number = t_PowerSystemInfo.
CompmentItem
GROUP BY t_Busrows.BUSROW, t_Busrows.CIRCUIT, t_Busrows.PANEL, t_Busrows.
PnlLoc, t_Busrows.MFG, t_Busrows.TRIP, t_PowerBoxInfo.BoxLocation,
t_PowerSystemInfo.CompmentItem, t_PowerEquipStandard.Mean_Amps,
t_PowerSystemInfo.ComponentPhaseA, t_PowerSystemInfo.ComponentPhaseB,
t_PowerSystemInfo.ComponentPhaseC, ([Mean_Amps]*[ComponentPhaseA])/100, (
[Mean_Amps]*[ComponentPhaseB])/100, ([Mean_Amps]*[ComponentPhaseC])/100,
t_PowerEquipStandard.Manufacture, t_PowerEquipStandard.Description,
t_PowerSystemInfo.SystemNumber, t_PowerSystemInfo.SystemComponentAlpha,
t_PowerSystemInfo.SystemName, t_PowerSystemInfo.DualPower, t_Busrows.mAMPA,
t_Busrows.mAMPB, t_Busrows.mAMPC, t_Busrows.mDATE
HAVING (((t_Busrows.BUSROW) Like “*†& [What Buss Row?] & “*â€));

Now, I think the HAVING statement is set up to make the parameter entry as
flexible as possible because it has wildcard characters at both ends. The
query is getting data from an assortment of tables, as you can see, and it’s
calculating a few items as well. The report itself is regular, no subreports
inside it. I could use some explanatory help on what the FROM-INNER JOIN-ON
statements mean (my reference book doesn’t explain it very well). From
what’s there, can you figure out why some text entries just don’t make it to
the report?

Ok, from what you are saying, it appears that the report is fine.
Something about the query is failing.

What is the exact query you are using? (View the query in SQL text mode
and post the SQL text).

Is more than one table involved?

Is it possible that "8WH2" is the total content of the field and that
"6AB42" is not the total content of the field but has other characters
in the field (leading spaces, etc.)?

Try using criteria with the Like operator and wildcard characters to see
if that works.
Like "*6AB42*"

If that does return your expected records (and perhaps others you don't
want) then try
Like "*6AB42"
to see if there is a leading character that you are not seeing. You can try
Like "6AB42*"
to check and see if there are trailing invisible-to-the-human-eye
characters.

'====================================================
John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
'====================================================

I am using a parameter query to gather specific text data from a table to
show in a report, and I know the text is in the table. If I request one

[quoted text clipped - 5 lines]

some help to tell me why this query-to-report will see some text and ignore
other text.

 

[John Spencer]

All those INNER JOINS mean that there must be a record in every table that
relates to the row to be returned.

FROM t_PowerEquipStandard INNER JOIN
(t_PowerSystemInfo INNER JOIN
(t_PowerBoxInfo INNER JOIN
t_Busrows
ON t_PowerBoxInfo.BoxBussConnect =t_Busrows.BUSROW)
ON t_PowerSystemInfo.SystemBoxLocation = t_PowerBoxInfo.BoxLocation)
ON t_PowerEquipStandard.Model_Number = t_PowerSystemInfo.CompmentItem

Which means if even if there is a value in t_busrows and there is no related
record in t_powerBoxInfo then there won't be any row returned

You might try changing all the INNER JOINs to RIGHT JOINS and see if that
solves your problem. A right join means that all records on the right side of
the join will be returned and if there are matching records on the left side
of the join the data from those records will be returned. If there is no
matching record then nulls will be returned in the columns for that table.

There are also LEFT JOINS that work similarly except the logic is flipped.

So try editing the FROM clause to read as follows.

FROM t_PowerEquipStandard RIGHT JOIN
(t_PowerSystemInfo RIGHT JOIN
(t_PowerBoxInfo RIGHT JOIN
t_Busrows
ON t_PowerBoxInfo.BoxBussConnect =t_Busrows.BUSROW)
ON t_PowerSystemInfo.SystemBoxLocation = t_PowerBoxInfo.BoxLocation)
ON t_PowerEquipStandard.Model_Number = t_PowerSystemInfo.CompmentItem

If you do this then you should see at least the information from the t_busrows
table that matches your criteria.

You can also speed things up a bit by using a WHERE clause instead of a HAVING
clause and since you are not doing any aggregation, use the DISTINCT keyword
and drop the GROUP BY section

Bottom line try the following SQL

SELECT DISTINCT t_Busrows.BUSROW, t_Busrows.CIRCUIT, t_Busrows.PANEL
, t_Busrows.PnlLoc, t_Busrows.MFG, t_Busrows.TRIP
, t_PowerBoxInfo.BoxLocation
, t_PowerSystemInfo.CompmentItem, t_PowerEquipStandard.Mean_Amps
, t_PowerSystemInfo.ComponentPhaseA, t_PowerSystemInfo.ComponentPhaseB
, t_PowerSystemInfo.ComponentPhaseC
, ([Mean_Amps]*[ComponentPhaseA])/100 AS PhaseALoad
, ([Mean_Amps]*[ComponentPhaseB])/100 AS PhaseBLoad
, ([Mean_Amps]*[ComponentPhaseC])/100 AS PhaseCLoad
, t_PowerEquipStandard.Manufacture, t_PowerEquipStandard.Description
, t_PowerSystemInfo.SystemNumber
, t_PowerSystemInfo.SystemComponentAlpha
, t_PowerSystemInfo.SystemName
, t_PowerSystemInfo.DualPower, t_Busrows.mAMPA, t_Busrows.mAMPB
, t_Busrows.mAMPC, t_Busrows.mDATE
FROM t_PowerEquipStandard RIGHT JOIN (t_PowerSystemInfo RIGHT JOIN
(t_PowerBoxInfo RIGHT JOIN t_Busrows
ON t_PowerBoxInfo.BoxBussConnect =t_Busrows.BUSROW)
ON t_PowerSystemInfo.SystemBoxLocation = t_PowerBoxInfo.BoxLocation)
ON t_PowerEquipStandard.Model_Number = t_PowerSystemInfo.CompmentItem
WHERE t_Busrows.BUSROW Like "*" & [What Buss Row?] & "*"

John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County

OK, here’s the complete SQL statement (thanks for telling me how to get it –
as I mentioned, I’m still pretty inexperienced but trying to learn):

snip



Now, I think the HAVING statement is set up to make the parameter entry as
flexible as possible because it has wildcard characters at both ends. The
query is getting data from an assortment of tables, as you can see, and it’s
calculating a few items as well. The report itself is regular, no subreports
inside it. I could use some explanatory help on what the FROM-INNER JOIN-ON
statements mean (my reference book doesn’t explain it very well). From
what’s there, can you figure out why some text entries just don’t make it to
the report?

Ok, from what you are saying, it appears that the report is fine.
Something about the query is failing.

What is the exact query you are using? (View the query in SQL text mode
and post the SQL text).

Is more than one table involved?

Is it possible that "8WH2" is the total content of the field and that
"6AB42" is not the total content of the field but has other characters
in the field (leading spaces, etc.)?

Try using criteria with the Like operator and wildcard characters to see
if that works.
Like "*6AB42*"

If that does return your expected records (and perhaps others you don't
want) then try
Like "*6AB42"
to see if there is a leading character that you are not seeing. You can try
Like "6AB42*"
to check and see if there are trailing invisible-to-the-human-eye
characters.

'====================================================
John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
'====================================================

I am using a parameter query to gather specific text data from a table to
show in a report, and I know the text is in the table. If I request one

[quoted text clipped - 5 lines]

some help to tell me why this query-to-report will see some text and ignore
other text.

 

[JimTrekker via AccessMonster.com]

John,
I started with your first idea and changed the INNER JOINs to RIGHT JOINs -
and it didn't work. The response when I tested the query was a small dialog
that said "No Current Record" regardless of the text string I entered. So I
changed them to LEFT JOINs just to see what would happen - and the query
performed identically to the INNER JOINs. Since the other ideas you gave are
apparently speed or performance improvements, I'll add them in after the
problem is fixed. Can you suggest something else to try?

jim

All those INNER JOINS mean that there must be a record in every table that
relates to the row to be returned.

FROM t_PowerEquipStandard INNER JOIN
(t_PowerSystemInfo INNER JOIN
(t_PowerBoxInfo INNER JOIN
t_Busrows
ON t_PowerBoxInfo.BoxBussConnect =t_Busrows.BUSROW)
ON t_PowerSystemInfo.SystemBoxLocation = t_PowerBoxInfo.BoxLocation)
ON t_PowerEquipStandard.Model_Number = t_PowerSystemInfo.CompmentItem

Which means if even if there is a value in t_busrows and there is no related
record in t_powerBoxInfo then there won't be any row returned

You might try changing all the INNER JOINs to RIGHT JOINS and see if that
solves your problem. A right join means that all records on the right side of
the join will be returned and if there are matching records on the left side
of the join the data from those records will be returned. If there is no
matching record then nulls will be returned in the columns for that table.

There are also LEFT JOINS that work similarly except the logic is flipped.

So try editing the FROM clause to read as follows.

FROM t_PowerEquipStandard RIGHT JOIN
(t_PowerSystemInfo RIGHT JOIN
(t_PowerBoxInfo RIGHT JOIN
t_Busrows
ON t_PowerBoxInfo.BoxBussConnect =t_Busrows.BUSROW)
ON t_PowerSystemInfo.SystemBoxLocation = t_PowerBoxInfo.BoxLocation)
ON t_PowerEquipStandard.Model_Number = t_PowerSystemInfo.CompmentItem

If you do this then you should see at least the information from the t_busrows
table that matches your criteria.

You can also speed things up a bit by using a WHERE clause instead of a HAVING
clause and since you are not doing any aggregation, use the DISTINCT keyword
and drop the GROUP BY section

Bottom line try the following SQL

SELECT DISTINCT t_Busrows.BUSROW, t_Busrows.CIRCUIT, t_Busrows.PANEL
, t_Busrows.PnlLoc, t_Busrows.MFG, t_Busrows.TRIP
, t_PowerBoxInfo.BoxLocation
, t_PowerSystemInfo.CompmentItem, t_PowerEquipStandard.Mean_Amps
, t_PowerSystemInfo.ComponentPhaseA, t_PowerSystemInfo.ComponentPhaseB
, t_PowerSystemInfo.ComponentPhaseC
, ([Mean_Amps]*[ComponentPhaseA])/100 AS PhaseALoad
, ([Mean_Amps]*[ComponentPhaseB])/100 AS PhaseBLoad
, ([Mean_Amps]*[ComponentPhaseC])/100 AS PhaseCLoad
, t_PowerEquipStandard.Manufacture, t_PowerEquipStandard.Description
, t_PowerSystemInfo.SystemNumber
, t_PowerSystemInfo.SystemComponentAlpha
, t_PowerSystemInfo.SystemName
, t_PowerSystemInfo.DualPower, t_Busrows.mAMPA, t_Busrows.mAMPB
, t_Busrows.mAMPC, t_Busrows.mDATE
FROM t_PowerEquipStandard RIGHT JOIN (t_PowerSystemInfo RIGHT JOIN
(t_PowerBoxInfo RIGHT JOIN t_Busrows
ON t_PowerBoxInfo.BoxBussConnect =t_Busrows.BUSROW)
ON t_PowerSystemInfo.SystemBoxLocation = t_PowerBoxInfo.BoxLocation)
ON t_PowerEquipStandard.Model_Number = t_PowerSystemInfo.CompmentItem
WHERE t_Busrows.BUSROW Like "*" & [What Buss Row?] & "*"

John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County

OK, here’s the complete SQL statement (thanks for telling me how to get it –
as I mentioned, I’m still pretty inexperienced but trying to learn):
snip

Now, I think the HAVING statement is set up to make the parameter entry as
flexible as possible because it has wildcard characters at both ends. The

[quoted text clipped - 41 lines]

 

[John Spencer]

Sorry, no other idea at this time.

'====================================================
John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
'====================================================

John,
I started with your first idea and changed the INNER JOINs to RIGHT JOINs -
and it didn't work. The response when I tested the query was a small dialog
that said "No Current Record" regardless of the text string I entered. So I
changed them to LEFT JOINs just to see what would happen - and the query
performed identically to the INNER JOINs. Since the other ideas you gave are
apparently speed or performance improvements, I'll add them in after the
problem is fixed. Can you suggest something else to try?

jim

All those INNER JOINS mean that there must be a record in every table that
relates to the row to be returned.

FROM t_PowerEquipStandard INNER JOIN
(t_PowerSystemInfo INNER JOIN
(t_PowerBoxInfo INNER JOIN
t_Busrows
ON t_PowerBoxInfo.BoxBussConnect =t_Busrows.BUSROW)
ON t_PowerSystemInfo.SystemBoxLocation = t_PowerBoxInfo.BoxLocation)
ON t_PowerEquipStandard.Model_Number = t_PowerSystemInfo.CompmentItem

Which means if even if there is a value in t_busrows and there is no related
record in t_powerBoxInfo then there won't be any row returned

You might try changing all the INNER JOINs to RIGHT JOINS and see if that
solves your problem. A right join means that all records on the right side of
the join will be returned and if there are matching records on the left side
of the join the data from those records will be returned. If there is no
matching record then nulls will be returned in the columns for that table.

There are also LEFT JOINS that work similarly except the logic is flipped.

So try editing the FROM clause to read as follows.

FROM t_PowerEquipStandard RIGHT JOIN
(t_PowerSystemInfo RIGHT JOIN
(t_PowerBoxInfo RIGHT JOIN
t_Busrows
ON t_PowerBoxInfo.BoxBussConnect =t_Busrows.BUSROW)
ON t_PowerSystemInfo.SystemBoxLocation = t_PowerBoxInfo.BoxLocation)
ON t_PowerEquipStandard.Model_Number = t_PowerSystemInfo.CompmentItem

If you do this then you should see at least the information from the t_busrows
table that matches your criteria.

You can also speed things up a bit by using a WHERE clause instead of a HAVING
clause and since you are not doing any aggregation, use the DISTINCT keyword
and drop the GROUP BY section

Bottom line try the following SQL

SELECT DISTINCT t_Busrows.BUSROW, t_Busrows.CIRCUIT, t_Busrows.PANEL
, t_Busrows.PnlLoc, t_Busrows.MFG, t_Busrows.TRIP
, t_PowerBoxInfo.BoxLocation
, t_PowerSystemInfo.CompmentItem, t_PowerEquipStandard.Mean_Amps
, t_PowerSystemInfo.ComponentPhaseA, t_PowerSystemInfo.ComponentPhaseB
, t_PowerSystemInfo.ComponentPhaseC
, ([Mean_Amps]*[ComponentPhaseA])/100 AS PhaseALoad
, ([Mean_Amps]*[ComponentPhaseB])/100 AS PhaseBLoad
, ([Mean_Amps]*[ComponentPhaseC])/100 AS PhaseCLoad
, t_PowerEquipStandard.Manufacture, t_PowerEquipStandard.Description
, t_PowerSystemInfo.SystemNumber
, t_PowerSystemInfo.SystemComponentAlpha
, t_PowerSystemInfo.SystemName
, t_PowerSystemInfo.DualPower, t_Busrows.mAMPA, t_Busrows.mAMPB
, t_Busrows.mAMPC, t_Busrows.mDATE
FROM t_PowerEquipStandard RIGHT JOIN (t_PowerSystemInfo RIGHT JOIN
(t_PowerBoxInfo RIGHT JOIN t_Busrows
ON t_PowerBoxInfo.BoxBussConnect =t_Busrows.BUSROW)
ON t_PowerSystemInfo.SystemBoxLocation = t_PowerBoxInfo.BoxLocation)
ON t_PowerEquipStandard.Model_Number = t_PowerSystemInfo.CompmentItem
WHERE t_Busrows.BUSROW Like "*" & [What Buss Row?] & "*"

John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County

OK, here’s the complete SQL statement (thanks for telling me how to get it –
as I mentioned, I’m still pretty inexperienced but trying to learn): snip

Now, I think the HAVING statement is set up to make the parameter entry as
flexible as possible because it has wildcard characters at both ends. The

[quoted text clipped - 41 lines]

some help to tell me why this query-to-report will see some text and ignore
other text.

 

[Geminde]

John,
I started with your first idea and changed the INNER JOINs to RIGHT
JOINs -
and it didn't work. The response when I tested the query was a small
dialog
that said "No Current Record" regardless of the text string I entered. So
I
changed them to LEFT JOINs just to see what would happen - and the query
performed identically to the INNER JOINs. Since the other ideas you gave
are
apparently speed or performance improvements, I'll add them in after the
problem is fixed. Can you suggest something else to try?

jim

All those INNER JOINS mean that there must be a record in every table that
relates to the row to be returned.

FROM t_PowerEquipStandard INNER JOIN
(t_PowerSystemInfo INNER JOIN
(t_PowerBoxInfo INNER JOIN
t_Busrows
ON t_PowerBoxInfo.BoxBussConnect =t_Busrows.BUSROW)
ON t_PowerSystemInfo.SystemBoxLocation = t_PowerBoxInfo.BoxLocation)
ON t_PowerEquipStandard.Model_Number = t_PowerSystemInfo.CompmentItem

Which means if even if there is a value in t_busrows and there is no
related
record in t_powerBoxInfo then there won't be any row returned


There are also LEFT JOINS that work similarly except the logic is flipped.

So try editing the FROM clause to read as follows.

FROM t_PowerEquipStandard RIGHT JOIN
(t_PowerSystemInfo RIGHT JOIN
(t_PowerBoxInfo RIGHT JOIN
t_Busrows
ON t_PowerBoxInfo.BoxBussConnect =t_Busrows.BUSROW)
ON t_PowerSystemInfo.SystemBoxLocation = t_PowerBoxInfo.BoxLocation)
ON t_PowerEquipStandard.Model_Number = t_PowerSystemInfo.CompmentItem

If you do this then you should see at least the information from the
t_busrows
table that matches your criteria.

You can also speed things up a bit by using a WHERE clause instead of a
HAVING
clause and since you are not doing any aggregation, use the DISTINCT
keyword
and drop the GROUP BY section

Bottom line try the following SQL

SELECT DISTINCT t_Busrows.BUSROW, t_Busrows.CIRCUIT, t_Busrows.PANEL
, t_Busrows.PnlLoc, t_Busrows.MFG, t_Busrows.TRIP
, t_PowerBoxInfo.BoxLocation
, t_PowerSystemInfo.CompmentItem, t_PowerEquipStandard.Mean_Amps
, t_PowerSystemInfo.ComponentPhaseA, t_PowerSystemInfo.ComponentPhaseB
, t_PowerSystemInfo.ComponentPhaseC
, ([Mean_Amps]*[ComponentPhaseA])/100 AS PhaseALoad
, ([Mean_Amps]*[ComponentPhaseB])/100 AS PhaseBLoad
, ([Mean_Amps]*[ComponentPhaseC])/100 AS PhaseCLoad
, t_PowerEquipStandard.Manufacture, t_PowerEquipStandard.Description
, t_PowerSystemInfo.SystemNumber
, t_PowerSystemInfo.SystemComponentAlpha
, t_PowerSystemInfo.SystemName
, t_PowerSystemInfo.DualPower, t_Busrows.mAMPA, t_Busrows.mAMPB
, t_Busrows.mAMPC, t_Busrows.mDATE
FROM t_PowerEquipStandard RIGHT JOIN (t_PowerSystemInfo RIGHT JOIN
(t_PowerBoxInfo RIGHT JOIN t_Busrows
ON t_PowerBoxInfo.BoxBussConnect =t_Busrows.BUSROW)
ON t_PowerSystemInfo.SystemBoxLocation = t_PowerBoxInfo.BoxLocation)
ON t_PowerEquipStandard.Model_Number = t_PowerSystemInfo.CompmentItem
WHERE t_Busrows.BUSROW Like "*" & [What Buss Row?] & "*"

John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County

OK, here’s the complete SQL statement (thanks for telling me how to get
it –
as I mentioned, I’m still pretty inexperienced but trying to learn):
snip

Now, I think the HAVING statement is set up to make the parameter entry
as
flexible as possible because it has wildcard characters at both ends.
The

[quoted text clipped - 41 lines]

some help to tell me why this query-to-report will see some text and
ignore
other text.

cincerely,hans,vienna,at.