https://www.infopathdev.com:443/forums/41.aspxIf you're not sure where to ask your question, ask it here. If necessary, our moderators will make sure it gets classified in the correct board.enCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/19604.aspxSun, 06 May 2007 03:36:00 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:19604Matt Faus0https://www.infopathdev.com:443/forums/thread/19604.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=19604Hi Trufooser, <br /><br /> I'm not exactly sure of your situation here, but it seems like are you running into some of the difficulties in working with secondary data connections in InfoPath. It is true that complex relationships from relational database tables are hard to manipulate in InfoPath, but without more information about your specific scenario we cannot confirm your claim.https://www.infopathdev.com:443/forums/thread/18037.aspxFri, 20 Oct 2006 16:12:18 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:18037trufooser0https://www.infopathdev.com:443/forums/thread/18037.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=18037I've been having a problem with the unique filter code as stated in this thread:<br /><br /<a target="_blank" href=http://infopathdev.com/forums/topic.asp?TOPIC_ID=3506>http://infopathdev.com/forums/topic.asp?TOPIC_ID=3506</a><br /><br />So I came up with an idea for a work around. I created another secondary datasource that queried the Lookup datasource. It created alias fields that joined two fields. In the thread from before, it combined Type and Area fields into one field, TypeArea. My idea was to then use this field to apply the unique filter on. However, I have discovered, that the only way a unique filter will work is IF AND ONLY IF the lookup entries are bound to a specific column (not the table) AND the unique filter is applied to only that selected column.<br /><br />Please confirm....