Documenting a Access Application for Developers

Posted by Nitrodist on Stack Overflow See other posts from Stack Overflow or by Nitrodist
Published on 2010-05-26T19:59:15Z Indexed on 2010/05/26 20:01 UTC
Read the original article Hit count: 230

I need to document a MS-Access application that was created, developed and maintained completely by a power-user over 10 years.

This is an interesting situation because what they want is a manual so that a future developer can come in without prior domain knowledge and make changes to the frontend or the backend in a timely manner.

There are a few questions on my mind for this little project:

  • What is a good manual design creating application? Microsoft Word doesn't quite cut it.
  • What kind of things would you, the developer, need to know in order to make changes to things like forms, reports, tables or other Access objects?
  • Anything else I missed? Any pitfalls?

© Stack Overflow or respective owner

Related posts about ms-access

Related posts about documentation