Sage 100

Has anyone developed a way to duplicate the SO_CustomerSalesHistoryWRK table? I realize the SOP is to modify an existing ""canned"" report using report settings, however, this end user would like to automate report distribution using Visual Cut so I do not believe modifying a canned report works in this particular situation. I have great fear that while the report layout may be creatable in Crystal with some work that the speed could be an issue.

You probably want to do that in SQL or Access.

Or open up their world to KnowledgeSynch possibilities....

If they are dead set on Visual Cut for automated distribution, you are going to be better off in the long run to re-create the report from scratch w/o using any WRK table even if you end up duplicating a canned report.

@RandyMarion I agree and worry about speed. Easy to start down the rabbit hole and then the customer doesn't like the report if it's slower.

Great options above. Just so you have 1 more in the mix, using JobOps as an example, they have a Crystal File Generation option from the JobOps / Custom Reports menu. Running it populates specific JT WRK files. This allows for example JT_TransactionWrk to be used in a custom Crystal report which is exactly what we did. Similarly an M/D type could create such a utility for SO_CustomerSalesHistoryWRK and even have it auto-run on a schedule.

At one point (maybe still) wasn't this a feature of Business Intelligence Reporter? I don't think I ever used it but I seem to recall they had a similar ability to use some work table-like files.

Yes in fact the BIR views may be the easiest way for Visual CUT. **Without** using BIR there is already a view (which will show up on the list of tables) called vCustomerSalesHistory. You can report off that right now w/o any BIR. If you're so inclined, you can take it a step further and use BIR to create a report based on that view (allowing you to link more tables if need be) and it will create a modified version of the view called View_CustSalesHist which would also be available to Visual CUT. For now just create a quick Crystal with vCustomerSalesHistory so you can see if it has all the fields that you need.