Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Developing DB Help File

Status
Not open for further replies.

bernie10

Technical User
Sep 13, 2004
219
US
I would like to include an (internal?) help file in my Access DB. The help file may be 10-15 pages. Does anybody have any suggestions about how this is usually done (or if it can be done)? I'd like to develop the help file and then tie it to a button on my form.

Thanks for any suggestions.

Collen
 
If you are actually creating a standard .HLP file or the latest MS standard (I forget the file extension), then you can use the Help Context Id property of the command button (Other Tab).

I havent tried it in Access, but have had success in other langauges, but I would expect it to work the same.

**********************************
There is more than one way to skin a cat...but who wants a skinned cat?
 
Thanks for the reply...

I really have no idea how to create a help file like that. I am just trying to create something to be contained in the DB that user's can pull up from the application and don't know where to start. Could you or anyone else offer some specifics about what I might do. Any thoughts or suggestions are appreciated.

Collen
 
To keep things really simple, I'd create a table with 3 fields:

ID: (autonumber)
Title: The title of the help
Helptext: The help you are providing

Then create a seperate form with just 4 controls (3xtextbox and an OK button)

textbox 1 to show ID of help file selected
textbox 2 to show Title of help file selected
textbox 3 to house the main help text of help file selected

Size the textbox3 to virtually fill the form so the help shown is all visible (or at least not much scrolling)

Then all you need to do is program the command button to open up this form and this form to get the ID maybe through the OpenArgs property.

If you are struggling, let me know and i will knock up a quick example.

**********************************
There is more than one way to skin a cat...but who wants a skinned cat?
 
Hmmm... thats a thought just using text boxes. I had a little more in mind something that could have formatting, maybe a screenshot, etc, though. Can this be done? I played with creating a report with the desired text, formmatting, etc. on it, but it got a little cumbersome. Perhaps that was the best approach for my purposes?

Thanks for your continued help.

Collen
 
i have just knocked up a quick version and there is a better way than using the Openargs property.

Simply use the 'WHERE ' clause of the DoCmd.OpenForm...e.g

Code:
DoCmd.OpenForm "Help", acNormal, , "ID = 2"

The only code you need in the Help form is to code the OK button to close the form.

Providing you set the record source of the form to the associated table and change a few properties of the form, you are off to a flyer.

**********************************
There is more than one way to skin a cat...but who wants a skinned cat?
 
You could do this...just include an extra field(s) as required (for a picture) and you just need a suitable container control on your form.

You could even include a sub-category field which to associate several help file records and allow the user to move from one record to the next in the help form so they can view the help you provide which would still be limited to the category in question.

**********************************
There is more than one way to skin a cat...but who wants a skinned cat?
 
Hi
Some versions (Office 2000 Professional for example) come with HTML Help workshop. I found this very useful as it is designed to work with Access and integrates with existing Access help, if you want it to. You can include screen shots and all sorts of HTML, such as links and fancy headings.
 
To make it really simple, if you have already created and formated (if that is a word lol) in Microsoft Word or Excel or txt whatever really, you could like the command button, link, picture or whatever directly to the help file (document in whatever format you have it in).

Just my two pennies.

Best of luck.
 
I've used both methods (custom form and HTML Help (CHM file)). What I've found:

* HTML Help is easier to apply fancy formatting, links between topics. Also they look more like other application help files, thus knowledge transferred from other applications is more easily understood. Can also create context sensitive help easily by assigning the context ID and application help file at the database level.
However:

* Access table with drop down list to select topic and ID: Easier to create and update, less flexible with regards to creating context sensitive help (must create "Help" button on each form to open the appropriate topic). Can easily create buttons to print current topic on the form as a report.

Overall, its 6 of one and half a dozen of the other; choose whichever suits your needs best. HTML Help workshop (the Microsoft compiler) is available from for free, but remember it needs IE on the PC regardless of the default web browser; older HLP files are still usable and don't require it to be present, but of course they are beginning to get a little outdated now.

See also if HTML help interests you.

John
 
Hello all,
Thanks for the many responses. Yall have given me quite a few different things to try. I will spend some time on it this week and follow-up with what worked or with additional questions.

Thanks again!

Collen
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top