InfoPath Dev

Got it!  Thanks.  OK Newbees:  Here is what I have learned.  If you are linked to a database, by default InfoPath assumes all fields are repeating fields.  So if you only intend to populate one record each time you use a table in your data source, it is very annoying because you keep getting a warning about binding ...

Hi all, and thinks Hilary for the support! Here is what I have learned in newbee terms: Query fields are for pulling information from your data source (particularly when you want to filter data).  Data fields can be used for both, pulling from and pushing data to your form. 

I really do want to see how you have done this, can you please resend in the 2010 format?

So, if add a second data connection (database), it is can only be "Receive Data" ... once that connection is set up, I only have data fields showing from that source (no query fields).  This doesn't make sense to me.  Wouldn't I want to filter what is coming back (i.e. need a query version of the field)?  And ...

Thanks for the quick reply and clearing it up, here is what I think you are communicating: Query feilds are used to bring data into your form and data fields are used to store data in your data source.  Some other thing (like placement or data connection) causes warnings about binding to repeating or non-repeating fields.

Thanks for the reply – but I am still confused.  In the right hand side of my InfoPath screen is a data connections list.  If I am connected to a SharePoint list or an access database, all of the fields in my data source are listed first as query fields, then again as data fields (note: they are the same (only one) field in the ...

So I have read hundreds of blog entries, and a book on InfoPath (Step by Step), and I still don't really understand the difference between data fields and query fields.  Can someone please explain in plain english what the two are used for and how they are different (with examples)? When I am linking to a SharePoint List or Access Data ...

Design questions:   Situation: We have projects that go through phases (business case, complete, implemented, validated, closed).  At each phase, new information is added, and it goes through reviews/approvals.  We need to be able to slice and dice the data in a variety of ways (demographic information and revenue ...

Hi - thanks for the response,  I am sure I probably overcomplicating it.  I can't open your attachment because I have InfoPath 2010.

UGH!  I am new to InfoPath, but I didn't think I was this stupid.  Hours on this problem, and I have tried many things. I have a drop down menu that selects an item (department code) from a 3 column SP list (department code, department description, & function - departments roll up into functions).  The user sees and ...