https://www.infopathdev.com:443/forums/44.aspx enCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/92639.aspxSun, 01 Sep 2013 22:11:13 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:92639Patrick Halstead0https://www.infopathdev.com:443/forums/thread/92639.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=44&PostID=92639<p>My guess is that InfoPath thought the result would be a single employee as opposed to multiple. If you modify the data connection and use the last name with two hits, InfoPath will be smarter and see that there can be two returned values. The first time you set up the data connection you probably used a query that only returned one value.</p>https://www.infopathdev.com:443/forums/thread/92555.aspxTue, 27 Aug 2013 19:24:35 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:92555ErinG0https://www.infopathdev.com:443/forums/thread/92555.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=44&PostID=92555<p>I have a drop-down field control that uses a data connection to a SQL view containing a list of all employees. I sort this by FullNm in the data connection. There are no filters or complex statements in the SQL connection. We have two employees with the same name.&nbsp; When I select them in the control, the additional employee data is the same for both employees. It&#39;s like it&#39;s not seeing them as separate database rows.&nbsp; However, if I pull the same data connection into Excel, the data is correct.&nbsp; It&#39;s also correct by just viewing via SQL Management Studio.&nbsp; What gives?&nbsp; It&#39;s like InfoPath is doing something odd with this data.&nbsp; Thoughts?&nbsp; I&#39;m using InfoPath 2010.&nbsp; The SQL view is on 2008 R2.<br /></p>