Prev: "Exit Access" Code
Next: Scrolling in VBA module
From: Dennis on 1 Apr 2010 22:45
Jack,

Thanks, I really appreciate your knowledge and assistance.

Dennis


From: Dennis on 1 Apr 2010 22:47
Douglas,

Thanks. I'll have to read up on AutoKeys macro.


Dennis
From: Dennis on 1 Apr 2010 22:50
Stuart,

I'm guessing that writing my help text in Word and save it as an htm file
would work?


Dennis
From: Stuart McCall on 1 Apr 2010 23:23
"Dennis" <Dennis(a)discussions.microsoft.com> wrote in message
news:6DC62053-C3EF-4C55-8715-C0C2EB5FF2FA(a)microsoft.com...
> Stuart,
>
> I'm guessing that writing my help text in Word and save it as an htm file
> would work?
>
>
> Dennis

Absolutely. Word will let you format things quite nicely. The files it
generates are a bit long-winded, but from your description of what you have
planned, the size of the resulting files will be pretty much irrelevant.
They'll definitely load fast enough on the slowest of modern machines.

The best place to store the files is (IMO) with the backend data file, so
when you need to update them you only have one set of files to replace.


From: Jack Leach dymondjack at hot mail dot on 2 Apr 2010 05:40
Do you mean the AutoHotKeys program that lets you script keystrokes on a
system or application level? This would have to be installed and configured
on each computer the app is distributed to, correct?

I've never used that with Access before... is there any particular advantage
to this above using the KeyDown event?

--
Jack Leach
www.tristatemachine.com

"I haven''t failed, I''ve found ten thousand ways that don''t work."
-Thomas Edison (1847-1931)



"Douglas J. Steele" wrote:

> You can also create an AutoKeys macro and map F1 to call a function.
>
> --
> Doug Steele, Microsoft Access MVP
> http://www.AccessMVP.com/DJSteele
> (no e-mails, please!)
>
> "Jack Leach" <dymondjack at hot mail dot com> wrote in message
> news:1180E0A1-0110-437D-98F8-1B56D8CCBF72(a)microsoft.com...
> > ahhhhh... F1! I used a button on all my forms to open the help page, but
> > I
> > think if you go to the Form's KeyDown event, you can capture F1 (I'm not
> > exactly sure how to reference that particular key, but some testing should
> > give an answer).
> >
> > Private Sub KeyDown(KeyCode As Integer, Shift As Integer)
> > If KeyCode = <F1 code> Then
> > KeyCode = 0
> > DoCmd.OpenForm frmHelp etc etc
> > End If
> > End Sub
> >
> > that might get you started anyway...
> >
> > --
> > Jack Leach
> > www.tristatemachine.com
> >
> > "I haven''t failed, I''ve found ten thousand ways that don''t work."
> > -Thomas Edison (1847-1931)
> >
> >
> >
> > "Dennis" wrote:
> >
> >> Jack,
> >>
> >> How did you capture the F1 function key (help key) for help or did you do
> >> something else?
> >>
> >> Dennis
>
>
> .
>
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: "Exit Access" Code
Next: Scrolling in VBA module