Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'd like to add here some other questions and answers related in a way or another to the same issue. The pointers might lead to my own answer to these questions, but do not hesitate to browse other's answers!</p> <p><a href="https://stackoverflow.com/questions/469436/ms-access-as-enterprise-software/471785#471785">MS Access as enterprise software</a></p> <p><a href="https://stackoverflow.com/questions/47400/best-way-to-test-a-ms-access-application/70572#70572">Best way to test an MS-Access application</a></p> <p><a href="https://stackoverflow.com/questions/247292/working-with-multiple-programmers-on-ms-access/250852#250852">Working with multiple programmers on MS-Access</a></p> <p><a href="https://stackoverflow.com/questions/393381/recommendations-on-using-sql-server-guid-from-ms-access/393522#393522">Recommendations on using SQL server GUIDS from MS-Access</a></p> <p>I must admit that one of the main constraints of Access is the limited object model. I was specifically annoyed by the lack of possibilities to add my own properties and methods to the Form object. I recently found an efficient turnaround to this problem by creating 2 extra objects:</p> <ul> <li><p>the "AllMyForms" object, which in fact maintain 2 object collections: one is the standard Access forms collection, the other one is a collection of all the instances of the "customForm" object. Both collections are indexed with the hwnd property of an opened form (or, to be more specific, the hwnd property of the instance of a form, allowing me to open multiple instances of the same form).</p></li> <li><p>the "customForm" object, which lists my custom properties and methods of a form's instance</p></li> </ul> <p>In this way, I can refer to properties such as:</p> <p><strong>accessForms:referring to the standard properties and methods</strong></p> <pre><code>AllMyForms.accessForm(hwnd).name </code></pre> <p>refers to the .name property of the access form through its .hwnd value</p> <p>By the way, the following debug.print will then give me the same result:</p> <pre><code>? screen.ActiveForm.name ? AllMyForms.accessForm().name 'default value for hwnd is screen.activeForm.hwnd' </code></pre> <p><strong>Custom forms:properties</strong></p> <pre><code>AllMyForms.customForm(hwnd).selectClause </code></pre> <p>will refer to the SELECT clause used to create the underlying recordset of the form's instance</p> <p><strong>Custom forms:methods</strong></p> <p>The .agregate method, available for a customForm object, will calculate the sum/min/max/avg of a form "column" (ie sum of values for a control in a continuous form):</p> <pre><code>AllMyForms.customForm().agregate("lineAmount","sum") </code></pre> <p>Will give me the sum of all "lineAmount" values displayed on the current/active instance of a form.</p>
    singulars
    1. This table or related slice is empty.
    1. POBest practices in Access programming
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USPhilippe Grondier
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POBest practices in Access programming
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI assume that your point about customer properties/methods is that you can't add them all in one place, i.e., that by default you have to add them in each form's class module? But this can be accomplished with a standalone class module wrapper around your forms, and it sounds like that's precisely what you've done. Can you clarify that?
      singulars
      1. PO
      1. USDavid-W-Fenton
    2. COWhile I understand the value of the customForm() wrapper, I fail to see the value of your custom forms collection. I don't see what it's providing that's not already available with the existing Access collections.
      singulars
      1. PO
      1. USDavid-W-Fenton
    3. COSome clarifications: the basic idea is to be able to add my own properties/methods to forms (meaning instances of Access forms). I have one unique procedure to open such an instance, with an "allMyForms.open myFormName, mySelectQuery (if any), etc" method. Each time this method is called, I will add one member to the o_AccessForms private collection, being a new instance of an existing form. I will also add one member to the o_CustomForms collection, being a new instance of my "customForm" object. By doing this I can access both standard properties and custom properties of my opened forms.
      singulars
      1. PO
      1. USPhilippe Grondier
 

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