Original Message:
Sent: 03-30-2025 12:10
From: Alnoor Cassim
Subject: Crystal Parameter Fields.
@Dan Burleson - Wow I never knew about the Session ID in the DSN trick! All this time I was needlessly doing the copying of session ID wrk file to base wrk file trick. Thanks for sharing that.
Also an xlnt reminder about leveraging worktable reports and creating a new report setting for that purpose, then joining additional tables to the worktable as needed. I've thought about using enforced joins before as a way to restrict data but have never played with it enough to properly see the restrictive effect. Now I will. I'm still a fan of sourcing UDFs from related tables to the worktable if that ends up making it so no other tables end up needing to be joined to the worktable at all.
(Separate Note: I also very much love what you shared in the past on how to send SQL commands to history tables in a subreport! )
------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)
------------------------------
Original Message:
Sent: 03-28-2025 19:20
From: Dan Burleson
Subject: Crystal Parameter Fields.
For Standard or Advanced (likely similar for Premium), if their report could be converted to use "AR_CustomerListingWrk", or if that worktable could be linked to their existing report by division and customer, then their report could replace the report of a designated Report Setting of the A/R Customer Listing report. This would allow them to use all the customer criteria available to that report to restrict the worktable and thus their report. To enforce the restriction, when linking the worktable, you must set the "Enforce Join" setting to "Enforce From" if the worktable links in the direction of "AR_Customer" or "Enforced To" if the worktable is linked from "AR_Customer". No hack, no limit.
There's no requirement to include fields from the worktable if it can't be completely replaced (Database menu, Set Data Location command) by AR_Customer.
Again for Standard and Advanced, if you want to test and preview data in the full version of Crystal, use the "Set Data Location" command to point to SOTAMAS90 for the tables, put the report in preview and leave it, check for the session work file in the ARxxx folder and grab the session id (that part of the name after "AR_CustomerListingWrk" and before the ".M4T") and store that in the SOTAMAS90 DSN "Login" panel in the "Session ID:" field.
------------------------------
Dan Burleson
Software Consultant
Connex Software
Corvallis OR
541-829-1054