Databases
StackOverflow2013
Usersdbo
USOliver
 

Note that there are some explanatory texts on larger screens.

plurals
  1. USOliver
    primarykey
    data
    text
    plurals
    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. POHow to enable debugging of stored procedures in visual studio?
      1. USOliver
      1. VTFavorite
    1. COYes, I do have multiple instances of Access, each for a different database/ADP. This is why GetObject(, "Access.Application") gets me nowhere/may return the wrong instance. I simply don't know the path of the database but I DO know (hopefully) the "Document Name" of the Databases (I created them), which doesn't need the path (works that way in Excel).
      singulars
      1. POWhat is the correct "Document Name" of an Access ADP/MDB to use in the GetObject("Document Name") call?
      1. USOliver
    2. COThe only solution is to hunt down each Variable/Control-Name and change the spelling to a common form. After an export and commiting the changes the names should be stable. Prefixing the control names with their types pretty much ensures through naming convention that the names don't collide with variables. (e.g. txtTitle for a textbox containing the Title field or cmbUsers for a combobox and so on)
      singulars
      1. PO
      1. USOliver
    3. COYes, this is a constant annoyance in our project also. As far as we have determined, the problem is that variables in your project have the same names as controls, just in different cases (up/low). Now, depending on the order of the modules being composed Access seems to take one spelling and "correnting" all the others, since VBA is supposed to be case insensitive. Access does this, even though the controls are on different forms! The problem gets bigger if you even have multiple controls of the same name in different cases on different forms.
      singulars
      1. PO
      1. USOliver
 

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