Question “How can I define a single autosearch parameter and apply it to multiple queries?” Solution Implement the Report.BeforeOpenDataPipelines event and use SQLBuilder to apply the AutoSearch value to additional queries. Download: ApplyAutoSearchValueTo2ndQuery.zip Sample RAP code: procedure ReportBeforeOpenDataPipelines; var lSQLBuilder: TdaSQLBuilder; begin {create SQLBuilder – pass the Customer2 datapipeline to the constructor} lSQLBuilder := TdaSQLBuilder.Create(Customer2); if (Report.AutoSearchFields[0].ShowAllValues) then Full Article…
Search the Wiki
Viewing 406 to 408 of 408 items
Custom Designers
Data Designers descend from TdaCustomDataWizard which is defined in daDataWizard.pas. The TdaCustomDataWizard class defines a class function called DataViewClass that should be overriden by descendants classes to specify the DataView class for which the data designer is implemented. The daRegisterWizard and daUnRegisterWizard procedures defined in daDataWizard.pas are used to register and unregister Data Designers with Full Article…
Custom Dataviews
The following code shows how to create a dataview in code: uses daDatMod, daQClass, daDataVw, daQuery, daDBBDE; {——————————————————————————} {TForm1.CreateDataView} procedure TDynamicReport.CreateDataView; var lSQL: TdaSQL; lTable: TdaTable; lField: TdaField; begin {create a datamodule – note: this is only necessary if you need to stream the report definition to an .rtm or database} FDataModule := TdaDataModule.CreateForReport(FReport); {create Full Article…