This content has been marked as final. Show 7 replies
See Peter Grainge's excellent web site for methods.
We use the URL call. And since we provide merged WebHelp, we also provide a flat file (we call formpath.txt) with a listing of which child project houses each form (window/screen, whatever), like this:
The form named aammainform is in the mwb_ug folder, and is named the same (if it were not, its actual name would be appended--following a backslash--after the folder name).
I have read Peter's site...several times, however, I believe the answer is at a level above that. In the actual VB program, there needs to be some type of call function (be it a class or form) that tells the program how to react when the help button is pressed.
The url call is easy enough to define....it is the vb code necessary to implement that call that is the step we are missing.
That is closer to what they are asking for (programmers are never happy, lol).
As a followup from them: is their some type of .dll, .ocx, or something like that is supplied by RH that they can use to help execute a help call?
Looks like we covered all the bases here...
I'll tell Morty you said 'Hi!'...
One durn moose kicked my dog this weekend.... he was hurtin', I tell yas...