The Detailed Aged Trial Balance is printing the Job number since version 9.0B. The report is almost twice in length now. Is there any option not to print the Job info?

Hi Softrak

Not to hijack the thread, but if you went to the trouble to add the job number, why didn't you also add the job name, especially with all of that extra space on the report.

To answer your question Patricia, no. Unless you can create a modified report and stick it in the ModRP folder.

Steve

Patricia:
Steve is right when he recommends modifying the report (CRAGETRL.rpt). Just be aware that if you modify the 9.0B file, it won't run when AR is upgraded to 9.0C (you'll need to make the modifications again). But the 9.0C version seems to run under 9.0B so make your modifications to the 9.0C file.

Thank you for your responses. I offered they already the ModRp altenative and I that it will need to be REDONE for the next update. It is a very expensive work around.

Patricia:
It's not that bad really. First, while I've never compiled any statistics on this, I would be comfortable saying that your modified version will usually work with a new version of AR. Of course Softrak may decide to make inclusion of the Job # a defined option in which case the problem disappears. And even if the report doesn't work, it's only a 20 minute change every 15 months or so (longer the first time admittedly).

Patricia: At the current time, the job number is not optional on the reports. I can add a suggestion to include an option on the respective reports to show or suppress this information, if the suggestion isn't already there.

Steve: Adding the job number (or job-phase-category estimate number) to the reports was easy because this information is already in the AR customer transactions file. Adding the job name or estimate description is more difficult because this information is not stored in AR transactions. Adding the link in the report to the JobCost data is not difficult per se, but having the report make a decision to read one JobCost file or the other (depending on the Job Tracking level) for every transaction to read the name/description will have a significant impact to the speed of printing the report. Having the name/description is a reasonable request, and many people would take the trade-off of information over performance, but not everyone would, which makes it not so simple under the surface.

Hi Softrak

I would be willing to bet that the vast majority of JobCost users track revenue at the Job level, in which case the Job Description is adequate, and there is no need for the Estimate Description.

I know that linking to the Job Master to get the Job Description is easy because I have modified the standard report myself to do it.

Steve