You are viewing limited content. For full access, please sign in.

Question

Question

Lookup fills too many rows in my table

asked on February 25, 2022 Show version history

I have a form that fills a table from SQL lookup table, however, it pulls ALL the rows from the lookup table. 

  • It is only supposed to fill rows based on a form number (the first column in the SQL Lookup table).
  • It is filling ALL rows from the lookup, regardless of the fact that it is told to fill only those of the indicated form number.

 

In my form design, the control is in placing the desired form number in the first column of the hazard table.  In my test case, I'm using FLHA3. 

The table then successfully fills with all the FLHA3 rows from the lookup table, but then it goes on to fill the table with all of the rest of the rows from the lookup table even though they have a different form number listed.

What am I doing wrong?

0 0

Replies

replied on February 25, 2022

You're third lookup rule doesn't have a condition, so it is going to pull every row from the table.

0 0
replied on February 25, 2022 Show version history

Thanks, Jason.  It wasn't allowing me a condition.  I don't know why, but every time I tried to add a condition, it removed the ability to click into the "as new rows" option.  Eventually, I discovered that if I added the fill options from the third lookup rule into the second lookup rule (eliminate the third rule), it worked.  I now have the table filling only the rows I want!

0 0
replied on February 25, 2022

Why does it grey out sometimes?

0 0
replied on February 27, 2022

The "as new rows" option will only be available when the condition use fields outside the table. If the condition uses the fields inside the same table, it will only fill the fields in the same row. 

1 0
replied on February 25, 2022

I think I got it!  Just double checking!

You are not allowed to follow up in this post.

Sign in to reply to this post.