Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

creating a help file

0 views
Skip to first unread message

kaosyeti@comcast.net via AccessMonster.com

unread,
Nov 14, 2005, 10:58:21 PM11/14/05
to
is there a way to create simple help file that i plan on linking to a command
button on a form using what's already in access? i will probably be giving
out this db that i've written to a number of other offices and the
instructions i'm going to have to pass along with them are SIMPLE. most
people who are the end users of this db are not computer saavy to say the
least.

what i have now is a command button that says 'press for help' and it will
open a form. the form is popup=yes and modal=yes. what i want in the form
is a word or wordpad file that may be longer than the window that pops up.
the problem, is that there are no scroll bars to be able to read up and down
the form's embedded file.

can i add these bars or is there a better way to do this?

--
Message posted via http://www.accessmonster.com

Larry Linson

unread,
Nov 15, 2005, 12:29:39 AM11/15/05
to

"kaos...@comcast.net via AccessMonster.com" <u15580@uwe> wrote in message
news:5761305a610df@uwe...

I created a two-field tblHelpTopics with a HelpID Field (AutoNumber) and
HelpTopic Field (Memo). I populated the first Record, which AutoNumbered as
1. I created a Form, with RecordSource of:

SELECT tblHelpTopics.HelpID, tblHelpTopics.HelpText FROM tblHelpTopics WHERE
(((tblHelpTopics.HelpID)=1));

as created with the Query Builder. On this Form I created a TextBox with
Control Source of HelpText, and in the Format page of its Properties Sheet,
set Scroll Bars to Vertical.

It works just as I expected it to work... I can use the scroll bars to show
text that does not initially show, or I can put the cursor in the text and
move it past the end of the visible text and it will scroll.

Are you saying that your Text Box in a Bound Form does not work this way?

Larry Linson
Microsoft Access MVP
I


kaosyeti@comcast.net via AccessMonster.com

unread,
Nov 15, 2005, 9:18:48 AM11/15/05
to
before you read this, please keep in mind that i'm new to access (6 weeks ago
is when i heard of it).

i followed what you have here and it almost worked. the only thing i can't
figure out is where the actual help text goes. your table is tblhelptopics
and your two fields are helpid and helptopic. should this be helpid and
helptext? based on your select statement, wouldn't this be trying to pull a
field called helptext when the helpid=1? and i assume that i can use this
same exact system to create other forms for help files (i need 3 total) where
the help id =2 and then =3 in the exact same select statement. i would just
have to create a new form for each one of those, correct? or is there a way
to assign a value to the command button that activates the helpfile form to
choose a helpid so that only one helpfile form can be written? OR am i just
missing something really obvious in the placement of my text that labels me a
total beginner?

Larry Linson wrote:
>> is there a way to create simple help file that i plan on linking to a
>> command

>[quoted text clipped - 14 lines]


>>
>> can i add these bars or is there a better way to do this?
>
>I created a two-field tblHelpTopics with a HelpID Field (AutoNumber) and
>HelpTopic Field (Memo). I populated the first Record, which AutoNumbered as
>1. I created a Form, with RecordSource of:
>
>SELECT tblHelpTopics.HelpID, tblHelpTopics.HelpText FROM tblHelpTopics WHERE
>(((tblHelpTopics.HelpID)=1));
>
>as created with the Query Builder. On this Form I created a TextBox with
>Control Source of HelpText, and in the Format page of its Properties Sheet,
>set Scroll Bars to Vertical.
>
>It works just as I expected it to work... I can use the scroll bars to show
>text that does not initially show, or I can put the cursor in the text and
>move it past the end of the visible text and it will scroll.
>
>Are you saying that your Text Box in a Bound Form does not work this way?
>
> Larry Linson
> Microsoft Access MVP
>I

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/databases-ms-access/200511/1

Larry Linson

unread,
Nov 15, 2005, 7:15:44 PM11/15/05
to
"kaos...@comcast.net via AccessMonster.com" <u15580@uwe> wrote

> before you read this, please keep in mind that i'm new to access (6 weeks

> ago
> is when i heard of it).
>
> i followed what you have here and it almost worked. the only thing i
> can't
> figure out is where the actual help text goes. your table is
> tblhelptopics
> and your two fields are helpid and helptopic. should this be helpid and
> helptext?

Yes, my fumbling fingers typed the wrong name.

> based on your select statement, wouldn't this be trying to pull a
> field called helptext when the helpid=1? and i assume that i can use this
> same exact system to create other forms for help files (i need 3 total)
> where
> the help id =2 and then =3 in the exact same select statement.

Yes, that is what I had in mind.

> i would just
> have to create a new form for each one of those, correct? or is there a
> way
> to assign a value to the command button that activates the helpfile form
> to
> choose a helpid so that only one helpfile form can be written? OR am i
> just
> missing something really obvious in the placement of my text that labels
> me a
> total beginner?

Yes, if you don't have a need to have more than one "help window" displayed
at a time, then you can use the same form.

The DoCmd.OpenForm statement can have either a Filter, or WhereCondition
(the wizard uses stLinkCriteria as the variable name for this one)
argument... its VBA code, but easy to build for this purpose, as you can
hard-code the value. Use the Wizard to build the command button and it will
write the code for you except for the following: Just before the
DoCmd.OpenForm insert the line

stLinkCriteria = "[HelpID] = 2"

where the number is the HelpID field of the Help Record you want to show.
The final think you will have to do is to put the cursor on the
DoCmd.OpenReport statement, press one, and choose the display format that
will make yours the Dialog you describe. You'll need to add a couple of
commas follwing the stLinkCriteria, then type "acDialog" without the quotes.

kaosyeti@comcast.net via AccessMonster.com

unread,
Nov 16, 2005, 2:53:29 PM11/16/05
to
it works perfectly. thank you. my only issue was with the 'memo' data type
in the table. i wasn't aware that you couldn't format some of the text
differently than other parts. i explored and found the ole object, went and
wrote my help file in word and tried to list it as an embedded object but i
keep getting an ole error. specifically, "The OLE server may not be
registered" error message. i searched the knowledge base a little but none
of their suggestions seemed to apply to my situation. i have office 2003 pro
edition and everything is run from the computer. i even ran the procedure
recommended in kb article 896865 and it didn't work. is there anything else
i can try or should i just give up and use a single format for the whole
thing?

Larry Linson wrote:
>> before you read this, please keep in mind that i'm new to access (6 weeks
>> ago

>[quoted text clipped - 6 lines]


>> and your two fields are helpid and helptopic. should this be helpid and
>> helptext?
>
>Yes, my fumbling fingers typed the wrong name.
>
>> based on your select statement, wouldn't this be trying to pull a
>> field called helptext when the helpid=1? and i assume that i can use this
>> same exact system to create other forms for help files (i need 3 total)
>> where
>> the help id =2 and then =3 in the exact same select statement.
>
>Yes, that is what I had in mind.
>
>> i would just
>> have to create a new form for each one of those, correct? or is there a

>[quoted text clipped - 6 lines]


>> me a
>> total beginner?
>
>Yes, if you don't have a need to have more than one "help window" displayed
>at a time, then you can use the same form.
>
>The DoCmd.OpenForm statement can have either a Filter, or WhereCondition
>(the wizard uses stLinkCriteria as the variable name for this one)
>argument... its VBA code, but easy to build for this purpose, as you can
>hard-code the value. Use the Wizard to build the command button and it will
>write the code for you except for the following: Just before the
>DoCmd.OpenForm insert the line
>
> stLinkCriteria = "[HelpID] = 2"
>
>where the number is the HelpID field of the Help Record you want to show.
>The final think you will have to do is to put the cursor on the
>DoCmd.OpenReport statement, press one, and choose the display format that
>will make yours the Dialog you describe. You'll need to add a couple of
>commas follwing the stLinkCriteria, then type "acDialog" without the quotes.
>
> Larry Linson
> Microsoft Access MVP
>
>

--

Larry Linson

unread,
Nov 17, 2005, 12:19:52 AM11/17/05
to
I haven't used Word as an OLE Server. But, you might check on a Windows
explorer window.... Tools | Folder Options | File Types and make certain
that the .DOC filetype is registered as Microsoft Word Document, and be sure
the file you are attempting to embed is a .DOC file.

But instead of using this approach, you might go to MVP Stephen Lebans site,
http://www.lebans.com, and look in the Site Table of Contents page for RTF.
He has a control that will display RTF, and you can save your Word documets
as RTF.

Larry Linson
Microsoft Access MVP


"kaos...@comcast.net via AccessMonster.com" <u15580@uwe> wrote in message
news:577619d4d7644@uwe...

Mike Preston

unread,
Nov 23, 2005, 8:09:53 PM11/23/05
to
On Thu, 17 Nov 2005 05:19:52 GMT, "Larry Linson"
<bou...@localhost.not> wrote:

>I haven't used Word as an OLE Server. But, you might check on a Windows
>explorer window.... Tools | Folder Options | File Types and make certain
>that the .DOC filetype is registered as Microsoft Word Document, and be sure
>the file you are attempting to embed is a .DOC file.
>
>But instead of using this approach, you might go to MVP Stephen Lebans site,
>http://www.lebans.com, and look in the Site Table of Contents page for RTF.
>He has a control that will display RTF, and you can save your Word documets
>as RTF.
>
> Larry Linson
> Microsoft Access MVP

Or, you can consider a non_ocx approach of multiple text boxes that
are sized to fit the text contained therein. Also a Lebansian (sm)
function. Search his site for fTextWidthOrHeight.

You can then code multiple helptext entries and change their
formatting appropriately. I have mine set to examine the first
character of the helptext entry and if it is a left brace, pull the
string out between that left brace and closing right brace. Once the
string is pulled out, it examines it for formatting tags such as "i"
for italic and "b" for bold. I also control fontsize by reference to
other characters (e.g., 2 means Font Size = 12). You can obviously
develop this to whatever extent makes sense.

The result is a series of separately formatted paragraphs, various
levels of indent, etc. that appear to be one continuous "help" screen.

Not as good as true rtf, but no ocx.

mike

0 new messages