Free Lessons
Courses
Seminars
TechHelp
Fast Tips
Templates
Topic Index
Forum
ABCD
 
Home   Courses   Index   Templates   Seminars   TechHelp   Forums   Help   Contact   Join   Order   Logon  
 
Home > TechHelp > Directory > Access > Normalizing Data < Prevent Duplicates | Date Math >
Back to Normalizing Data    Comments List
Upload Images   Link   Email  
Reports pulling IDs not Values
Debra Triolo 
       
2 years ago
So I went through and normalized some of my data, but now when I pull reports it is picking up the "ID" numbers for the normalized fields for some items instead of the actual values. Some of the values its picking up correctly.  I am not sure why it is "mixing and matching".  Please help.  Example:  I have a table of products set up with a ProductID and I am wanting to show the Products on my report.  It is linked to the product field but for some customers it is pulling the ProductID instead of the Product Name.
Debra Triolo OP 
       
2 years ago
Does anyone have any suggestions? I tried tying the report back to the product names, but it still picks up the ID number. I tried tying it back to the junction table but it instead duplicated products for every business line instead of just picking up the individual line items as entered into the main table.
Adam Schwanz 
            
2 years ago
Is it in a combo box? If so, what is the row source and bound column set to?
Debra Triolo OP 
       
2 years ago
Yes.  The originals are both tied to combo boxes.  The product combo box pulls off the product table and the business line combo box pulls off the business line table. The report is tied to a query that includes fields from the main table that includes both of the combo boxes as well. The drop downs have the actual names of the products and LOBs, but in the main table the LOBID and ProductID are stored in the LOB and Product field, so that is what is coming up on the report.  Everything worked fine until I went to run the report.
Alex Hedley 
            
2 years ago
Build a query that joins the tables on the relationship keys, then use that as the Report Source
Debra Triolo OP 
       
2 years ago
Hi Alex.  I tried that.  When I built the query I used the fields from the main tasks table and took the LOB and Product fields from their respective tables, but then it duplicated the tasks for each LOB Product regardless of what the task dictated in the main table. It was odd.  I have my relationships set up between the smaller tables and the main table and you would think it would pull it correctly, but it did not and I am at a loss as to why it is doing this.
Alex Hedley 
            
2 years ago
What's the underlying SQL for that query?
Debra Triolo OP 
       
23 months ago
The report is run off a query that pulls the LOB field and Product field in, along with the activity name and the ID of the person who is assigned the task. As I mentioned, the data has been normalized, so the LOB and Products are now housed in separate tables with LOBID and ProductID and in the task table under the product name or LOB name instead of the name.. it shows the numeric ID value- which is what it is supposed to do when you normalize (according to the videos I have watched).  My question is how do I reverse this so that when I run the report it gives me the actual string values (names) rather than ID numbers?  Is the only answer to go back and undo the normalization and put everything back into one table?
Debra Triolo OP 
       
23 months ago
Some structural background:  The LOB and Product fields are combo boxes made with the wizard that get their data from their respective tables.  The Active LOB table has only the following fields : LOBID, LOB and the Active Product Table has ProductID and Product.   The row source for the LOB combo box is based on a query and the in the row source it says: SELECT [Active LOBsQ].[Lines of Business] FROM [Active LOBsQ] ORDER BY [Lines of Business];  (again the wizard did all this) when it asks where I want to store the values I tell it to store them in respective field in the main task table- under LOB. The drop down for the combo boxes have all the correct names. No issues there at all. But in the table it is storing the LOBID instead of the name. On the report it gives the LOBID instead of the name too.
Debra Triolo OP 
       
23 months ago
Also the respective tables are linked to the actual main via LOBID and ProductID with no referential integrity checked. I need to get this fixed before Tuesday AM. Please help. I have spent all weekend trying to figure out a solution.  I really dont want to rebuild all my tables and pages...

This thread is now CLOSED. If you wish to comment, start a NEW discussion in Normalizing Data.
 

 
 
 

The following is a paid advertisement
Computer Learning Zone is not responsible for any content shown or offers made by these ads.
 

Learn
 
Access - index
Excel - index
Word - index
Windows - index
PowerPoint - index
Photoshop - index
Visual Basic - index
ASP - index
Seminars
More...
Customers
 
Login
My Account
My Courses
Lost Password
Memberships
Student Databases
Change Email
Info
 
Latest News
New Releases
User Forums
Topic Glossary
Tips & Tricks
Search The Site
Code Vault
Collapse Menus
Help
 
Customer Support
Web Site Tour
FAQs
TechHelp
Consulting Services
About
 
Background
Testimonials
Jobs
Affiliate Program
Richard Rost
Free Lessons
Mailing List
PCResale.NET
Order
 
Video Tutorials
Handbooks
Memberships
Learning Connection
Idiot's Guide to Excel
Volume Discounts
Payment Info
Shipping
Terms of Sale
Contact
 
Contact Info
Support Policy
Mailing Address
Phone Number
Fax Number
Course Survey
Email Richard
[email protected]
Blog RSS Feed    YouTube Channel

LinkedIn
Copyright 2024 by Computer Learning Zone, Amicron, and Richard Rost. All Rights Reserved. Current Time: 12/14/2024 6:00:30 AM. PLT: 1s