DADE End User Help

rbuser

I'm working on the end user help for our application and I've run into
something that I can't figure out.

On the Data Tab of the end user report designer, none of the windows displayed
from that portion of the report designer respond to F1 keypresses. As such,
the OnHelp event of the report designer component is never called so I can't
process the help request. Additionally, I don't see any PlugIn register type
calls in the DADE forms to allow for custom DADE wizards.

Is there any way to either enable the call to the report designer OnHelp from
the DADE portions of the report designer or override the override the DADE
form components and assign help contexts to them directly? Or am I just
missing something obvious here?

--

---------------------------------------
Terry Swiers
Millennium Software, LLC
http://www.1000years.com
http://www.atrex.com

Atrex Inventory Control/POS -
Big business features without spending big business bucks!

Atrex Electronic Support Options:
Atrex Knowledgebase: http://www.atrex.com/atrexkb.cfm
Email: mailto:support@atrex.com

nardmoseley

There is no Help events being fired from the Dade windows, that is correct.

It is possible to create custom QueryDesigner and QueryWizard forms and
register them with ReportBuilder. The following article explains how to
accomplish this...


----------------------------------------------------------------------------
------
Tech Tip: Implementing a Custom Data Designer
----------------------------------------------------------------------------
------

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
DADE.

For an example of a data designer, see daQueryDesigner.pas which contains
the default QueryDesigner. The TdaQueryDesigner class overrides the
DataViewClass method to return TdaQueryDataView. Therefore, the
QueryDesigner is used with any descendant of TdaQueryDataView
(TdaADOQueryDataView, TdaBDEQueryDataView, etc.).

For an example of registering a Data Designer, see the initialization and
finalization sections of daIDE.pas.

Note: To replace an existing Data Designer, unregister the default designer
first:

initialization

daUnRegisterWizard(TdaQueryWizard);
daUnRegisterWizard(TdaQueryDesigner);

daRegisterWizard(TmyCustomQueryWizard);
daRegisterWizard(TmyCustomQueryDesigner);

finalization

daUnRegisterWizard(TmyCustomQueryWizard);
daUnRegisterWizard(TmyCustomQueryDesigner);






--