netcode Posted February 12, 2009 Posted February 12, 2009 Hey there, I am trying to get a total of ALL the records in the portal, related or not. Maybe using "portal" is not the correct wording because the data is in a table, and portals only show related records. But here is how it is set up.. I have a sponsor table and a ticket table. A sponsor can request tickets, when an employee finds out a sponsor wants tickets they enter in the # of tickets that the sponsor as requested. I want the total of ALL tickets that have been requested across all sponsors. I tried using summary fields and summary parts but summary parts seem to only calculate data on a group of records currently being browsed. And as the user is browsing through records based on the sponsor table the summary fields are only calculating the related records. Any suggestions would be wonderful :
bcooney Posted February 12, 2009 Posted February 12, 2009 You need to create a summary field in your Ticket table. It, too, will reflect the Total of Qty in tickets for the found set. This can be useful if you want to find date ranges or types, etc. The other choice is to create a relationship from your Sponsor table to Tickets using the "x" join option. This will see all ticket records. Then create a calc, TotalTickets = sum ( Sponsor::Ticket~all:Qty).
netcode Posted February 12, 2009 Author Posted February 12, 2009 thanks bcooney. in regards to creating a summary field in the ticket table.. that will do the trick.. IF your layout is based off the ticket table. If your browsing the sponsor table that summary field will only calculate the related records. I found my solution, just create a report (columnar) that uses the ticket table. Then the summary field works and I have my totals : I don't think what I initially wanted is possible, to be browsing the sponsor table yet still see a summary of records in the ticket table. Anyways thanks for the input!! :)
bcooney Posted February 12, 2009 Posted February 12, 2009 Actually, if you re-read my post, I offered two solutions. One, a summary in the ticket table (yes, using a layout based on Tickets) or a sum ( ) from Sponsors using a cartesian relationship to tickets.
Recommended Posts
This topic is 5855 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now