Without seeing the entire dicts for both files, it's hard to say for sure, but on the face of it it sounds like the query should be on the TRANS file with translates back to the ACCOUNT file.
> On Mar 12, 2014, at 5:56 PM, [email protected] wrote: > > > >> On Sunday, March 9, 2014 2:01:46 PM UTC-4, Kevin Powick wrote: >> A dict item does not provide summary information for an entire file. >> >> Unfortunately, you haven't really described your end goal, only what you're >> trying to do with a dict item. What are trying to ultimately accomplish? >> Are you trying to produce a report with specific information, such a summary >> totals? >> >> -- >> Kevin Powick > > > > Thank you for your response. We are electronically pushed information on > collection accounts from our client - such as the name of the debtor, > address, etc. in a file called ACCOUNT. ACCOUNT does not contain a history > of payments, which is very important to us. We are also pushed transaction > information in a separate file called TRANS, described above. TRANS contains > payment information (along with a lot of irrelevant noise such as account > adjustments and incremental interest), but those payments are split to > different "buckets" across accounts. For example, a $100 payment may be > split $50 to principal, $25 to interest and $25 to collection costs. I am > trying to reassemble these split transactions to identify the $100 payment > using a dictionary item, by taking each account number and adding the actual > payments (marked by a "3" in attribute 9) for each date together in a sum. > > My thought would be then to use the dictionary item to export and write a > file of just the actual payments per date per account that I could access > from ACCOUNT using a translate dictionary item. But I am not really sure how > I will solve the many-to-one problem (one account number may have a multitude > of payments over time, making it difficult to make the account number the > primary key for a translate lookup). > > The long and the short of it is that I am trying to do something that is > probably better left to a PICK BASIC program, but I haven't learned PICK well > enough to do it yet. > > >> > > -- > -- > IMPORTANT: T24/Globus posts are no longer accepted on this forum. > > To post, send email to [email protected] > To unsubscribe, send email to [email protected] > For more options, visit this group at > http://groups.google.com/group/jBASE?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "jBASE" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- -- IMPORTANT: T24/Globus posts are no longer accepted on this forum. To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en --- You received this message because you are subscribed to the Google Groups "jBASE" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
