Database Instructions

  • Thread starter Thread starter Krista
  • Start date Start date
K

Krista

I am trying to write Instructions for a database that I built. I started
writting them as a report but it will only allow me to make it so big. I
haven't used Data Access Pages yet would this be a better route to go. I
don't want to put these over the internet I just want them available as a
reference to the user either to just look at on the monitor or to print off
and use. Any Ideas are welcome.
 
Wouldn't instructions be records in a table? Then bind the report to the
instructions table.
 
That may work but, after writing just a portion of the instructions, I have
ended up with a lot information and I just think it would be easier if I
could write them on a page. I don't know if it would be possible to write up
a page using word and then just link it to the database or if it would be
easier to use the Data Access Page. I have a startup page and I want a link
from there to open the instructions, I have people that will be using this
that are very computer weary.
 
If you don't want to use Access as a database then consider just placing
your instructions in Word or another application. You can then store the
file name in Access and open the file when necessary.

I would still consider placing instructions in records in tables.
 
Hi,

Have you thought about creating a compiled help file? I'm not sure but it
sounds like that's what you want. In the Access 2000 help system look for
an article called "Create a compiled Help file that is displayed when you
press F1". I found the link when I went to the index in help and typed
"Help", look for "Create custom Help for a form."

Hope this helps,
Linn
 
I've created some quick & dirty User Guides in Word using screenshots,
graphics, bookmarks & internal hyperlink jumps within the document. I then
save the file as a HTML archive doc in the same directory as the mdb/mde. I
add a "Users Guide" button & Menu option in the application that points to a
file with that name in the same path as the backend Data file. The Users
Guide will open in their browser & they can view or print as they wish. Of
course, if they open the file in Word, they can easily modify the file as
well.

That's one reason I don't save it as a .doc file: it would open in Word & it
would be too easy to make accidental changes. Saving it as HTML means it
automatically opens read-only in the user's browser (there may be exceptions
to this, but I think they would be few and far betweeen). In addition, the
document COULD be easily modified by the user if they go to the trouble of
opening it from within Word or another HTML editor (it ain't Hamlet, after
all). Flexible, yet secure enough for most cases.
 
Back
Top