replied on January 5, 2017
Hey AJ,
Regarding the amount of lookups you can have before experiencing performance slowdowns. This is really a "it depends" kind of answer based on a variety of factors (i.e. the complexity of the stored procedures/lookups).
Forms does try to process lookups as fast as it can, but the browser has a limit on how many connection you can make at a time. So you must wait for some to come back before the next set it sent. You can take a look at this link for further information or you can also check the activity yourself with Fiddler.
As for the second point regarding the sequence of lookups. The order matters if say the input in field 1 triggers a lookup to populate field 2, which then does the same for field 3. Otherwise the order does not matter.
In the first scenario, we send the order during the lookup and older value should not mess with the newer value. We do not know when the lookup will return so how it looks to the user might change. For example if you get the newer value returned first it will change one time. But if the older value comes first and then the newer it should flip twice. But they should end on the same value.
Hope that helps!
Cheers,
Kevin