Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I would have to see your table to be sure but the issue might be GoToRecord offsets the number specified from the beginning of the recordset. This means that if you have an address id of 51 it will take you to record 51 in theory. </p> <p>The problem with using this method is that if you delete any <code>AddressID</code> then 51 will not be the record you want because it is taking you to the 51st record regardless of <code>AddressID</code>.</p> <p>For Example I add 100 Records to Addresses with IDs 1-100 then I delete the first 99 of them and I am left with <code>AddressID</code> 100 if I use this command I will receive the standard "You can't go to the specified record." becuase I am telling access to go to a record that does not exist. </p> <p>Please check you table to make sure that all the <code>AddressID</code> fields are exactly in order and let me know. Generally I would not recommend this as a method of navigation. </p> <p>Is <code>AddressID</code> a auto-increment number in access? Are you guaranteeing that an address will never be deleted? </p> <p>Try this</p> <pre><code>'expression.SearchForRecord(ObjectType, ObjectName, Record, WhereCondition) Docmd.SearchForRecord acForm,"NavigationSubform",,"AddressID=" &amp; addr_id </code></pre> <p>This will actually search the record set for the WHERE condition specified and Go To that record. Note this goes to the First record it finds which should not be a problem since you are using an ID.</p> <p>Using Filter</p> <pre><code>With Me.NavigationSubForm.Form .Filter = "AddressID=" &amp; addr_id .FilterOn = True End With </code></pre> <p>This will only show the results with that Address ID in the subform </p>
    singulars
    1. This table or related slice is empty.
    1. PODoCmd.GoToRecord adding 1 to target record
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USengineersmnky
    1. USengineersmnky
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODoCmd.GoToRecord adding 1 to target record
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThank you. +1 for trying to help. I tried your DoCmd.SearchForRecord syntax, but it is giving me runtime error 2489, the object NavigationSubform is not open. Of course, I also tried the name of the form and also Forms!Main!NavigationSubform.Form!NavigationSubform.Form and others, but I still get runtime error 2489. Any suggestions for how to reference the navigation subform, given the correct information about how to reference its sourceobject in my original posting above?
      singulars
      1. PO
      1. USCodeMed
    2. COIF you do not need navigation ability in the subform you can use filter. I do this a decent amount instead of directly linking subforms in access. I have added the code to my answer
      singulars
      1. PO
      1. USengineersmnky
    3. COThis works now, so I am going to mark yours as the answer. I did have to replace your Me with the actual Forms!Main!NavigationSubform.Form!NavigationSubform.Form because Me refers to a textbox in this context. But the code works after I made that small change. Thank you for your help.
      singulars
      1. PO
      1. USCodeMed
 

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