R
Randy Coates
Because my InfoPath form's main connection has a many-to-one
relationship, I wonder if that is causing this issue, but here are the
details. I have three query fields. Two are derived from the main
table ("many" side) of the main connection, and the third is derived
from the secondary table ("one" side) of the main connection. The two
from the main table work just fine; the query returns the correct
results. The one query field from the secondary table might as well
not even be on the form; entering a value there and clicking the query
button does not show signs of using that condition. Can anyone verify
for me that a many-to-one also destroys the use of the "one" table's
query fields within InfoPath?
Randy Coates, Allin Consulting
relationship, I wonder if that is causing this issue, but here are the
details. I have three query fields. Two are derived from the main
table ("many" side) of the main connection, and the third is derived
from the secondary table ("one" side) of the main connection. The two
from the main table work just fine; the query returns the correct
results. The one query field from the secondary table might as well
not even be on the form; entering a value there and clicking the query
button does not show signs of using that condition. Can anyone verify
for me that a many-to-one also destroys the use of the "one" table's
query fields within InfoPath?
Randy Coates, Allin Consulting