Whats the best way to add a bit of a help file into an access file

[jerry.ranch]

Say, on a data entry form

a "HELP" cmbBUTTON that bounces the user off to word file that has
help, or is there some other way to do it (like a label object with
help on another form)

Thanks
Jerry

[Jeff]

Something I have done that works well and is very simple is to have a single
table with 3 fields. One for the form name, one for a title and one for the
help details.

On each form that needs help - simple ones don't - you either add a button
with the familiar ? character, or the word 'Help'. When the user clicks on
it, it pops up a form that is filtered to the form name and gives the
relevant help. You can of course pretty this up and add a shortcut key etc.

To edit the help I have made it so that holding the 'shift' or 'control' key
when clicking on the button opens the form in edit mode so someone can be
nominated to actually write the help. I hate writing help, and developers
don't make good help authors.

This doesn't include any searching or index etc but the help is always
relevant to the current form.

Depending on your needs this sort of thing may be suitable.

Jeff

<je*********@pi oneer.com> wrote in message
news:gt******** *************** *********@4ax.c om...

Say, on a data entry form

a "HELP" cmbBUTTON that bounces the user off to word file that has
help, or is there some other way to do it (like a label object with
help on another form)

Thanks
Jerry

[Jerome Ranch]

Thats a good idea Jeff
I like it. Don't care about the searching.

One aspect of help are the field definitions.
I do have a field definition file...a list of all the available fields
and what data is contained in each. I think the user will want to use
this.

This would be too big to place in any one field (due to formatting
etc,) but I suppose I could place a link in a field to a doc file?
Jerry

Something I have done that works well and is very simple is to have a single
table with 3 fields. One for the form name, one for a title and one for the
help details.

On each form that needs help - simple ones don't - you either add a button
with the familiar ? character, or the word 'Help'. When the user clicks on
it, it pops up a form that is filtered to the form name and gives the
relevant help. You can of course pretty this up and add a shortcut key etc.

To edit the help I have made it so that holding the 'shift' or 'control' key
when clicking on the button opens the form in edit mode so someone can be
nominated to actually write the help. I hate writing help, and developers
don't make good help authors.

[Jamey]

I've bee doing something similar lately using the Assistant Object.
I've got a hidden table with an indexed list of all forms and controls
from which I pull the necessary 'Heading' and 'Text' properties for the
assistant's balloon. I've been implementing it for the past few weeks
on a new database I've been working on. The module for it is pretty
darn busy code-wise, but I've set it up, more or less like a What's
This button. I've got it working in a multi-user environment, which
seems to work best when the Assistant Object is assigned to a public
variable.

It seems like a pretty good way to supply help with simple forms, and
I've even included functionality to reindex periodically based on the
latest modification to the form and to allow someone designing a form
of their own to include the same functionality on their own forms.

Took a while to work the kinks out, but it's working well now.

I worked for a long time with the "supposed" HTML Help functionality
used with the HelpContextID property, but that had some major pitfalls.

Otherwise, I generally include a link of some kind in my form's footer
or on a menu or toolbar to go to application specific help either
written in HTML or ASP depending on the circumstances. For that, you
can reference the HelpContextID property.

[Jeff]

Why not just add a couple of extra text field to the table for hyperlinks to
related documents. You could have at the top of your form a small heading
titled 'See also' followed by these links and then your main text. Make all
controls transparent with a white form and it will look and work well.

I have never had need to reference another document, but will keep it in
mind my self.

Jeff

"Jerome Ranch" <ra*****@mchsi. com> wrote in message
news:tu******** *************** *********@4ax.c om...

Thats a good idea Jeff
I like it. Don't care about the searching.

One aspect of help are the field definitions.
I do have a field definition file...a list of all the available fields
and what data is contained in each. I think the user will want to use
this.

This would be too big to place in any one field (due to formatting
etc,) but I suppose I could place a link in a field to a doc file?
Jerry