WhizBase SubReports

Due to its simplicity and unique way of working with databases, single WBSP file can work with single recordset regardless of recordsets complexity. However, in most real-life situations  there is the need for using more than one recordset for a single task (in a single wbsp file). For that purpose  WhizBase uses subreports - a report that is inserted in another report. When you combine two or more reports, one of them must serve as the main report (main WBSP file).
To include subreport in main WBSP file use either $WBSR or $WBSRQ functions. Although subreport file looks very similar to ordinary WBSP file, there are few differences:

• Subreport can only execute Q command (i.e. it is not possible to add, delete or modify data using subreport)
• It reads only a subset of WBSP variables - mostly those related to database recordset:
  FormFields section
  WB_BaseName, WB_ShowEmpty, WB_LCID , WB_DBObject, WB_WC, WB_InsBR, WB_StartRec, WB_MaxRec, WB_RcdSet, WB_TempName, WB_Query, WB_SetADOCompatible, WB_ChangeHFOn, WB_Order, WB_Exclusive, WB_ReadOnly, WB_Connect, WB_Last, WB_Usr, WB_Pass, WB_System, WB_Predicate, WB_Group, WB_Having, WB_DBFlds
  MsgAndLbl section
  WBM_NoMatch
  Including any other WBSP variable in subreport will not generate the error, but the additional variables will be ignored.
• WB_Query variable in subreport file has different behavior compared to same variable in ordinary WBSP file - it is possible to include $wbf, $wbrf, $wbfc, $wbfu and $wbff functions in wb_query variable and when any of these are included they should be written using report syntax (with square brackets) and not input syntax (with braces). Any occurrence of these functions will be replaced with proper content from superior recordset (one defined in main WBSP file)
• Subreport ignores all code that is above <body...> and bellow </body> tags, including the tags itself.

Subreports recordset can, but does not have to,  be related to the data in the main report. For example, you can use the main report to list publishers and subreport to list titles published by them.

In this example main report uses table "Publishers" to list publishers in detail section and then uses subreport to show titles published by current publisher. Unique identification for every record in table "Publishers" is field PubID. In table "Titles" publisher is identified with field PubID (also in every record). Setting WB_Query to this value will generate subreport for every record in table "Publishers" and every subreport will contain only those records from table "Titles" where PubID field has the same value as PubID field of publishers recordset.
Subreport files can have any extension you want. The .sr extension in the example is used to separate subreport from main WBSP file.

For security reasons it is good policy to name subreport files with extension .sr. It is because WBSP server-side configuration variable HideDocuments in default value include .sr extension, which means that WBSP will return HTTP error 404 (File not found) whenever someone tries to execute any .sr file directly (e.g. by typing its URL in browsers address bar).