Databases
StackOverflow2013
Postsdbo
PODocumenting a Access Application for Developers
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODocumenting a Access Application for Developers
    primarykey
    data
    text
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USNitrodist
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODocumenting a Access Application for Developers
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODocumenting a Access Application for Developers
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'd say as a developer I'd prefer good code commenting, uniform naming conventions and good design over a document I'll likely never read. When you say "without prior domain knowledge" it's not clear if you mean of Access or of the specific application. If the former, good luck with that -- you could write a book. If the latter, see my first comment!
      singulars
      1. PODocumenting a Access Application for Developers
      1. USDavid-W-Fenton
    2. COI mean, the way the business operates as the 'domain knowledge' source. There are a *lot* of quirks, unexpected business rules and other behaviors that I've spent the couple weeks learning about that are extremely relevant to how the database is set up and how the application works as a whole.
      singulars
      1. PODocumenting a Access Application for Developers
      1. USNitrodist
    3. COTrouble is these kinds of documents are seldom updated once they're done. Maybe the idea of a Wiki which the users create would be an idea. And the idea is that any new users *always* post their question(s) in the wiki and then get the answers and update them. And they have to be given the time to do so. Also why not do this within the Access app. Create a table with one field by form name and another memo field. Each form gets a button which opens a form against that table creating/update the record corresponding to that form. Then the users update the memo field right there.
      singulars
      1. PODocumenting a Access Application for Developers
      1. USTony Toews
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload