tonys wrote:Thanks.
So therefore if a standard report has a formula that is used by one of your stored procedures like "Pass_SP_StartingGRNNo"
This formula name is "hard coded" into the system ?
I copied the report and renamed the formula to Pass_RecNo and it did not work (no records returned)
There is no hard and fast rule - in the case of the GRN in the form we look for the formulas "Pass_SP_StartingGRNNo" and "Pass_SP_EndingGRNNo" and set those values for you - we did that to try and support older non-stored procedure based reports, as well as stored procedure based reports.
A good rule of thumb is if we have a standard report using a stored procedure, then your custom one should have the same Pass_SP_* formulas and the same contents in the JiwaRanges formula as our standard one, then you'll know it will work.
We recognise this is a bit clunky and are working toward a better, more consistent report interface so it's not so hit-and-miss. As SAP's support with Crystal seems to be less focused on MSSQL (read: more interested in HANA support), we're looking at alternate reporting engines, but will support SAP Crystal Reports as long as SAP provide MSSQL support. Already we're seeing
stubbornness by SAP to support Azure SQL, so I'm convinced the writing is on the wall in terms of future support for MSSQL by SAP Crystal Reports.
Mike