RE: Should be simple but...

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi Duane,

No, I had not considered that because I was unaware of this property. I
tried it; changing it from "No" to "Yes". Unfortunately, it didn't work. The
subreport consists of two text boxes with a Control Source of LastName for
one and FirstName for the other. When I look at the subreport preview, I see
it hides the last name for those staff who are affected, but leaves the first
name visible.

This does not affect my sample report because I have not input all staff,
but it doesn't hide the duplicate names I do have on the report. I realize
that sounds a bit confusing. What I mean is that if the employee is
*different* (same last name but the first name is different), it will hide
the last name. If it is the same employee (the only difference being the
phone #), it doesn't hide the first or last name. The report appears
unchanged.

I understand if it can't be done. I was just wondering if there was a way to
do it.
--
Aria W.


"Duane Hookom" wrote:

Have you considered using the Hide Duplicates property?

--
Duane Hookom
Microsoft Access MVP


"Aria" wrote:

First you state: "sorted by last name, first name and then phone location"
Then you have only 2 levels and I can't figure out why you would have a
group header for Last Name.

OK, I kept thinking about this statement and couldn't sleep so I got to
work. When I created the reports I think it was my first time dealing with
sorting and grouping levels. I mis-interpreted something I read in the Help
file and ended up with a group header for Last Name.

I just wanted you to know that I deleted that group header and put the
controls in the detail section. It works now! How easy was that! I knew I
was making it too complicated.

Can I ask one last question? Is there any way that I can get it to just list
the employees' name once and then list all the phone #s associated with that
employee (still grouping using last name first)?

Thank you so much for the push in the right direction!
--
Aria W.


"Duane Hookom" wrote:

First you state: "sorted by last name, first name and then phone location"
Then you have only 2 levels and I can't figure out why you would have a
group header for Last Name.

Can you give a more complete and accurate description of your report and
subreport with the groupings and location of the subreport? What is in the
subreport and how is it linked to the main report?

Looking back through multiple postings and trying to make sense of them
makes my head spin.
--
Duane Hookom
Microsoft Access MVP


"Aria" wrote:

I'm sorry Duane. I didn't think think the subform mattered since I'm not
having a problem with the reverse directory and it's pulling the same
information but in a slightly different order. Ummm...I'm afraid I'm going to
need help with this. I tried using the subform/subreport wizard but it
doesn't look the way I would like. The Phone Associations subform has a
delete row button which I do not want to show on a report but when the wizard
finished there it was.

Currently, the recordsource is the query (qryPhoneReportCampusPhones).

"True Values of the Sorting and Grouping levels?"
I'm sorry to be such a novice. I'm not quite sure what you mean here. I can
tell you what I see and maybe that will help you, help me.

Sorting and Grouping (All groupings are ascending.):
Last Name
********
Group:
Header, yes
Footer, no
On, Each value
Interval, 1
Keep Together, No

First Name, Phone Description/Location, Phone #
********
Group Header, No
All other groupings same as above.

Thank you for your help.




--
Aria W.


"Duane Hookom" wrote:

You kinda blind-sided us by not mentioning anything in your first post about
"subform". If this is truly a subform, change it to a subreport.

Then tell us about the record sources of your main report & subreport, their
link master/child properties. We should also get the true values of your
sorting and grouping levels.

--
Duane Hookom
Microsoft Access MVP


"Aria" wrote:

Hi Duane,
Thank you for responding. The phone type values are:
1= District cell
2= campus phone

There is a text box for phone number and a subform listing the employees
associcated with the phone number. There *should* be 6 phone listings for the
office, 2 per person. Each person only has one. Since it is my office that
seems to be having the issue, I can confirm that the data is correct.

What section of the report am I displaying the data? Hmm...is that the
problem? It's displaying in the LastName Header.

--
Aria W.


"Duane Hookom" wrote:

I would confirm the phonetype values and just check your data. The query
looks fine. What section of the report are you displaying the data?
--
Duane Hookom
Microsoft Access MVP


"Aria" wrote:

Hello,
This should be simple but maybe I'm missing something easy. I have multiple
versions of phone directory reports for our school. I am not experiencing
problems with the mobile/cell phone directory nor the reverse directory by
location. So far, it list everyone as it should.

I seem to be having a slight problem with the staff directory. It is sorted
by last name, first name and then phone location. There can be multiple staff
members assigned to a location phone. I have one location that lists 6 staff
members to a phone. No problem here. My problem is the office phone. There
are 3 staff employees assigned to the office phone as well as their direct
line phones. The report list 2 of the staff members for the office phone and
only one for the direct/desk phone. All 3 staff employees should be listed
for the office phone as well as 3 seperate entries for direct lines. Thank
you for any ideas or suggestions.

Here's the SQL:
SELECT tblPhonesEmps.PhoneID, tblPhonesEmps.EmpID, tblEmployees.LastName,
tblEmployees.FirstName, tblPhones.PhoneNumber, tblPhones.PhoneDescription,
tblPhones.PhoneType
FROM tblPhones INNER JOIN (tblEmployees INNER JOIN tblPhonesEmps ON
tblEmployees.EmpID = tblPhonesEmps.EmpID) ON tblPhones.PhoneID =
tblPhonesEmps.PhoneID
WHERE (((tblPhones.PhoneType)=2))
ORDER BY tblEmployees.LastName, tblEmployees.FirstName;

--
Aria W.
.

Quantcast