\Michael didn’t say whether he was doing single record or scanning lookups. I agree with Dave’s answer for the former and believe it also applied in Pan6. I don’t think it applies to the latter, eg. consecutive FormulaFill Lookups, each is a separate search in both Pan6 and PanX. If I’m wrong I’d be delighted to be corrected.
They could be reduced to one cross database scanning search by using Superlookup and having its dataformula collect a text array for each record: Field1+Sep+Field2+Sep+Field3 etc. with an appropriate separator. The found text array entries could then distributed to other fields via a series of FormulaFill Array( statements. This can be faster than multiple scanning FormulaFill Lookup searches between databases. I haven’t tried it, but presume the same could be done using data arrays.
A functionally equivalent, albeit more complicated, approach would be to first collect the Field1+Sep+Field2+Sep+Field3 etc. array, for all records to be searched, in the database to be searched, either into a dedicated field or within one of the fields previously searched separately. FormulaFill Lookup (superlookup or otherwise) that collective field once, distribute its found array entries as above, then convert back the searched database to its pre-collected state. This involves more steps and temporarily (you hope) changes the searched database, but in my experience it sometimes is faster than the simpler, safer first method. I don’t understand why it can be faster, but if speed is important it may be worth trying and doing some comparative speed testing.