Data Environment Tab, Report Properties Dialog Box (Report Builder) (TMM)

If you associate a report’s DataEnvironment with a VCX DataEvironment class, the ReportBuilder writes binding code in the DataEnvironment BeforeOpenTables event, like this: 

*-----------------------------------------------------*
* THIS METHOD CODE WAS INSERTED BY THE REPORT BUILDER *
*-----------------------------------------------------*
LOCAL loMember, laDEEvents[1], liMember, liMembers, loBoundMember
THIS.AddProperty( "BoundDE", ;
   NEWOBJECT( "deClassName", "classlibrary.vcx" ))
IF VARTYPE( THIS.BoundDE ) = "O" AND;
   UPPER( THIS.BoundDE.BaseClass ) = "DATAENVIRONMENT"
                       
   * Bind events here, skipping the Init and Destroy.
                       
   [..]

Previous to SP1, the “classlibrary.vcx” literal string in the code above always contained the fully-pathed class library name of your nominated class library. This behavior was helpful during report design; with the fully-pathed filename, you can preview from the Report Designer without needing to ensure that the classlibrary is available on your PATH or loaded library list. You can edit the generated code to remove the path before delivering the report with applications, if desired.

However, in SP1, the ReportBuilder has a new checkbox that allows you to choose how this code is generated: Use full path. This option makes the Data Environment -loading feature more flexible, and was included in SP1 to encourage its use in future extension code.