Results 1 to 3 of 3
  1. #1
    Join Date
    Jan 2013
    Posts
    2

    Unanswered: Access2010 database - Clickable reports

    I have a database consisting of one table.
    Some rows in this table have fields that contain the ID number of other rows. (as a value)
    I have created a report of this database.
    I would like to click on those ID numbers in the report and be taken to the row that corresponds to them (otherwise I would have to scroll down the page and do it manually)
    Similar to the idea of hyperlink, except for I want to be directed to a different page on the same report.
    I am using Access 2010.

    Thank you

  2. #2
    Join Date
    Feb 2004
    Location
    New Zealand
    Posts
    1,472
    Provided Answers: 10
    Report are for print out thats why they are called reports

    Why not just put a dropdown box "combobox" and findfirst that will then take to the rigth recored
    Last edited by myle; 01-02-13 at 17:15. Reason: Spelling
    hope this help

    StePhan McKillen
    the aim is store once, not store multiple times
    Remember... Optimize 'til you die!
    Progaming environment:
    Access based on my own environment: DAO3.6/A97/A2000/A2003/A2007/A2010
    VB-NET based on my own environment started 2007
    SQL-2005 based on my own environment started 2008
    YOUR PASSWORD IS JUST LIKE YOUR TOOTHBRUSH DON'T SHARE IT.
    DONT WORRY ABOUT THOSE WHO TALK BEHIND YOUR BACK
    THEY'RE BEHIND YOU FOR A REASON

  3. #3
    Join Date
    Jun 2005
    Location
    Richmond, Virginia USA
    Posts
    2,764
    Provided Answers: 19
    In addition to myle's correct statement about Reports being intended for Printing out data, not for the navigation/manipulation of same, your explanation of your app is highly suspect!

    Having the the same ID Number in multiple Records, in a single Table, simply makes no sense! The situation you appear to be referring to is normally handled with a Main Form/Subform scenario.

    I think you really need to give us a plain language explanation of what you're trying to accomplish, in order for us to help you.

    Linq ;0)>
    Hope this helps!

    The problem with making anything foolproof...is that fools are so darn ingenious!

    All posts/responses based on Access 2003/2007

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •