Joined: 02 Jun 2011
Location: South Africa
Online Status: Offline
Posts: 47
Posted: 07 Jun 2011 at 6:44am
There
needs to be a logical relationship between fields that you link the tables on.
So if you have a customer table with a customer number you can link it to a
sales table on the customer number. Both of these tables, customer and sales,
might have an internal ID field, but linking on the ID fields is meaningless.
Joined: 11 Mar 2011
Location: United States
Online Status: Offline
Posts: 251
Posted: 07 Jun 2011 at 12:22pm
There are so many ways to link tables that sometimes you have to play around with the links.Sometimes just changing the link to a left or right outer link will fix things and sometimes you have to add another table that you don't need any information from in order to add a table you do.I'd try a left outer link and see if that doesn't cure it.You may also be running into a null value and that will kill a report especially if you're using a formula.
Joined: 19 Dec 2008
Online Status: Offline
Posts: 9053
Posted: 08 Jun 2011 at 4:20am
also keep in mind that crystal joins are not "automatically enforced" when they are added to a report as they are in something like SQL. Just making the join in SQL will alter your returned data set based on the join.
In Crystal you either enforce the join in the Link Options in the DB Expert links tab or the join becomes enforced when when you use any 1 field from both tables that are joined. They can be used in any fashion in the report (referenced in formula or the select expert or just a field in the report canvas).
This explains really odd behavior when you have a report that is showing all your records, you add one field to the canvas or a formula (the first use of any field in a table) and all of the sudden your data rows disappear or go to a huge number (enforcing a cartesion product of a join).
Joined: 11 Mar 2011
Location: United States
Online Status: Offline
Posts: 251
Posted: 08 Jun 2011 at 11:27am
If they are holding true to being double each time a quick easy fix would be to create a formula for that field and divide by 2.Something like {Table.Field}={Table.Field}/2 should do it.
Joined: 18 Oct 2010
Online Status: Offline
Posts: 37
Posted: 09 Jun 2011 at 9:22am
Thanks again for the help. I really appreciate it.
I changed the report so it only selects distinct records. That fixed the 2X problem I had on the quantities. However, the report now only includes terminated employees. It used to include both terminated and active employees.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum
IP Logged
