"Bob Darlington" wrote in message
news:5174984b$0$2258$c3e8da3$40d4...@news.astraweb.com...
>Any recommendations for a alternative Help software package?
I say roll your own.
The trick is a simple + good design.
Here is functional spec for my help system - I not had time to write this,
but it been in my head for at least 10 years!!
===
You know, really in about 5 hours of time you could build in a VERY nice
help system. Maybe even less.
Albert's REALLY short functional spec for a Access Help system:
Purpose:
Help system will be based on a table of rich text memos to allow nice help
text formatting with colors – a color scheme similar to most help files
would also enhance this look + feel.
The help code system would simply be broken down into this:
Application help table file – single record and memo to explain the
application (accounting system, or PO system – a short explain). Kind of
the "about" this application memo - no need to have this be a long book.
Forms help menu – single memo that explains the use + intention of the
current form.
Forms controls (sub table/form) of above.
These memos would be for each control. Hitting f1 in a given form would
launch this memo. If this control des NOT have a memo, then the above form
level memo would then be displayed (with a sub list of possible controls
that can be clicked on to view the help files for each control).
So above is a simple set of two tables with rich text memos, and also a
keyword column.
The help system would thus simply when the user hits F1 do this:
Get current form name (
screen.ActiveForm.name). Then we get current control
name. We then query our forms help table (with a join to the child controls
table) and launch the appropriate memo based on the two columns (form name
and control name). As noted, if no control name exists or is found, then try
again the query with JUST the form name).
We then pull up the help for the control, or if none, then help for the
whole form.
To create the help system once in place on the fly without code?
The help system will have two modes:
Design + create help mode.
user mode
In design + create mode you simply hit f1 on any form while running the
application. The help system looks for the form level memo (and if one is
not found THEN YOU a prompt asking do you want to add a form level help item
for the current form name. You then GET TO EDIT + ADD this form level memo.
You type in the form description and what is supposed to do - and you can
use nice fonts since we have rich text now).
You ALSO then get to edit/add the sub form record with the current control
name (if one had the focus). You thus edit the help text for the control.
When you save, next time you hit f1, then the memo from that control (based
on form + control) menu is displayed (and you can edit the text).
You could in fact run the application ALWAYS in this way for help. That way
ALL USERS of the system could in fact build the help file for you!!!
So you just sit down a non programmer and let them have at your application.
They can open any form and start hitting F1 for each control and add the
help text (or edit help text if that control been done).
When done (or you are never done), you simply flip the help system into
"user" mode. Now when users hit f1, they see the memo pop up, but cannot
edit it.
The above system would thus allow you to build a help file system on the fly
or even have a "user" and non program person edit + create the help file by
simply opening each form and moving into a control and then hitting f1 key.
======
End of Albert's help spec.
So the above is what we call in the software industry a functional spec. It
is a general outline of the concept and idea of how this help system would
work.
This type of help generator system was popular back in the old FoxPro days,
and the new Access rich text memo ability's we had since 2007 make Access
absolute perfect for this type of help file system.
The beauty of the system is you don't have to generate help IDs, and when
done you could build a few reports that printout what each form does. Since
when you hit f1 in a given form a new record in the forms help table is
created (or displayed for the user to edit). So when done, could also add a
top most help screen in which they get the main application help and then a
sub form list of all forms with the form description and perhaps even a
first line of the memo displayed in that sub form
And you could even build a report that shows the form name, the form memo
help text and as a sub report shows all of the control names along with the
memo text for each control (the formControls table).
So to build a slick automated help building system in which NO code or no
help ID's or managing of attaching help text to form or controls is required
could be done with such a system.
As noted, it is really rather simple system to build – I estimate a basic
working copy of such a system could be coding in less one day of developer
time, if not a few hours.
Just build two or 3 tables, and have a form that pops up to edit the help
text in a large text box.
So I say roll your own. A starting idea for using rich text and building
your own help file can also gleaned from this article.
http://blogs.office.com/b/microsoft-access/archive/2009/04/23/write-your-own-help.aspx
Best regards,
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
PleaseNoS...@msn.com