That's good to hear. It suits a lot of our use cases where we are currently using LookupResources. A rough question on performance - do you have a rough estimate of the number of tuples above which it may be more efficient to use LookupResources?