-
Shashank S
- PowerBuilder
- Wednesday, 25 March 2026 10:49 AM UTC
We are currently migrating an application from Sybase PowerBuilder 12.5.2 ( WinForms target help page using PBDOTNET) to Appeon PowerBuilder Classic 2022R3.
In the existing code, we used the following .NET-based help invocation:
#IF DEFINED PBDOTNET
System.Windows.Forms.Help.ShowHelp(_parent, ls_help_file, _hn.KeywordIndex, ls_help_key)
#END IF
Since PBDOTNET is not supported in Appeon Classic, we are replacing this with native PowerBuilder functionality.
We attempted to use the Help() function as follows:
Help(aw_parent, ls_help_file, Keyword!, ls_help_key)
However, we encountered:
C0051: Unknown function name: Help
From initial analysis, this seems to be related to the context where the function is being called (non-window object / DataWindow).
Questions:
- What is the recommended approach in Appeon Classic to replace System.Windows.Forms.Help.ShowHelp()?
- Is Help() the correct replacement, and if so, what is the proper way to invoke it from non-visual objects?
- Are there any limitations with Keyword! navigation when using CHM help files in Appeon?
- Is using Run("hh.exe ...") considered a reliable alternative in production scenarios
Any guidance or best practices for handling help file integration during PBDOTNET → Appeon Classic migration would be appreciated.
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.