|
|
|
|
|
Peachtree Accounting Community :
Crystal Reports for Peachtree :
Re: JrnlHdr.GoodThruDate
|
|
|
|
|
|
|
|
|
Re: JrnlHdr.GoodThruDate
|
|
 TomA
Sage Employee
Posts: 96
Registered: 08-18-2008
Message 1 of 7
Viewed 146 times
|
|
|
I know exactly how you feel! DOH!!! Tom A
|
|
|
|
11-05-2009 11:23 AM
|
|
|
|
|
|
Re: JrnlHdr.GoodThruDate
|
|
pwalto
Contributor
Posts: 19
Registered: 05-15-2009
Message 2 of 7
Viewed 148 times
|
|
|
Tom, Imagine that! It works. All that fusing over a simple setting, I can't say how I feel at the moment since we are on a public board.... Thanks again...peg
|
|
|
|
11-05-2009 10:51 AM
|
|
|
|
|
|
Re: JrnlHdr.GoodThruDate
|
|
TomA
Sage Employee
Posts: 96
Registered: 08-18-2008
Message 3 of 7
Viewed 152 times
|
|
|
Peg, The only thing I can think of without seeing the actual report and digging into it deeper is that in your GoodThruDate group you have it set to group by the week instead of by each day. That is the only way that I can somewhat reproduce the same behavior. If you up attach your Crystal Report to the post, I will be more than happy to take a look it for you. But unless I have the actual report, I don't know that I will be able to trouble shoot it much more for you. Tom A
|
 Accepted Solution
|
|
|
11-05-2009 09:45 AM
|
|
|
|
|
|
Re: JrnlHdr.GoodThruDate
|
|
pwalto
Contributor
Posts: 19
Registered: 05-15-2009
Message 4 of 7
Viewed 156 times
|
|
|
Tom, Thank you, here is a small section of the output, please notice the good thru dates are a day or two on either side of the GoodThruDate it is doing the grouping on, Need by: 6/21/2009 (1st grouping on Jrnlhdr.GoodThruDate) PO#: 16DUM1 Vendor Name: TESTER2 TransactionDate 5/26/2009 Job no/Cust NO : Test (2nd grouping Jrnlhdr.reference/PO#)Internal Notes: Test for the internal note retrieval 6/24/2009 (jrnlhdr.goodthrudate) PO#: 16DUM2 Vendor Name: TESTER2 TransactionDate 5/26/2009 Job No/Cust No TEST Internal Notes: Test for internal note retrieval 6/25/2009 A few notes, All the information in the report is contained in the second grouping, there is no detail section, the intent of the report is to show the open POs their good through date, vendor, date the PO was entered and internal notes. The idea is to show overdue POs, and hence we would like them sorted by GoodThruDate. If I move everything into a detail section except for the 1st grouping, I get a line for each item on the PO, which I do not want. I thought that in itself was strange, since I thought there would only be one jrnlHdr record per PO created, not multiples, I thought there would be multiple jrnlRows. Once I moved all items into the 2nd grouping that problem went away. The data contained within the second grouping is correct per the PO that was entered. And as you can see the jrnlhdr.goodthrudate is different than that in the 1st grouping or what is listed as Need By. As mentioned previously the selection expert is using only: {JrnlHdr.JrnlKey_Journal} = 10 and
{JrnlHdr.POSOisClosed} = 0 Database linkages are: JrnlHdr, Vendors: Linkage CustVendID to VendorRecordNumber (left outer Join) I appreciate all your help..Thanks...Peg
|
|
|
|
11-05-2009 09:31 AM
|
|
|
|
|
|
|
|
Re: JrnlHdr.GoodThruDate
|
|
TomA
Sage Employee
Posts: 96
Registered: 08-18-2008
Message 6 of 7
Viewed 166 times
|
|
|
pwalto, I'm not experiencing the save behavior. Can you upload a copy of your report so I can take a look at it? Tom A
|
|
|
|
11-04-2009 04:14 PM
|
|
|
|
|
|
JrnlHdr.GoodThruDate
[ Edited ]
|
|
pwalto
Contributor
Posts: 19
Registered: 05-15-2009
Message 7 of 7
Viewed 174 times
|
|
|
I am creating a report that has a first grouping using JrnlHdr.GoodThruDate. I'm specifically trying to pull purchase orders using: {JrnlHdr.JrnlKey_Journal} = 10 and
{JrnlHdr.POSOisClosed} = 0 Here is what's odd, it is seemingly grouping the POs correctly, yet everywhere I print the JrnlHdr.GoodThruDate, its just a couple days off in either direction of the actual date that is entered in the "good thru" date of the Purchase Order window. Am I printing/pulling from the wrong field? I looked through the .dat files and I can't find another field that seems to be correct. Message Edited by pwalto on 11-04-2009 12:00 PM
|
Solved!
 Go to Solution
|
|
|
11-04-2009 11:48 AM
|
|
|
|
|
|
|
|
|
|
