How to lookup stored records/data using an InfoPath 2003 form? - InfoPath Dev
in

InfoPath Dev

How to lookup stored records/data using an InfoPath 2003 form?

Last post 07-28-2009 01:40 PM by PPBWH. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 07-28-2009 11:53 AM

    • PPBWH
    • Not Ranked
    • Joined on 06-02-2009
    • Posts 8

    How to lookup stored records/data using an InfoPath 2003 form?

    Hi,

      Currently there are 4 records that have been entered in my Infopath form but this form will eventuall hold several hundred records. Is there a way to insert a combo box or drop-down box in an infopath form so that a person can click on the box and lookup ID numbers or names and so when they pick, for example ID 401, the InfoPath form is filled with ID 401's information?

     I want to do this so that if many records have been entered and a user want to go back and change a field's value on record #xxx, they can simply look up the record using the combo box or drop-down box. Thanks.

  • 07-28-2009 01:28 PM In reply to

    Re: How to lookup stored records/data using an InfoPath 2003 form?

    Hi -- is this a data base bound form? If so, you can add fields to your form from the 'query' fields section of your data source, let the users select some values, then run the query associated with the main data source. You could use a secondary data source to populate the drop downs, and just select the column you need from your table for the data for the drop down. Here's an MSDN lab that might help you.

    Hilary Stoupa

  • 07-28-2009 01:40 PM In reply to

    • PPBWH
    • Not Ranked
    • Joined on 06-02-2009
    • Posts 8

    Re: How to lookup stored records/data using an InfoPath 2003 form?

    HI,

     Thanks for the response. I will do as you suggested. Yes, the form is bound to an Access database.

    Also, why is it that when you put a "Run Query" button in the form, and there are let's say 25 records in the database bound to the form, the query shows all the fields for all the records. You suggested solution would solve this problem by putting a filter on the "Run Query" button, correct?

     

     

Page 1 of 1 (3 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.