Dom,
Look Up fields pass information from a Parent Record to a Child Record. So if Table A is the Parent in your architecture, information from Table B cannot be a look up field in Table A.
Here is a quick ERD that shows the behavior.
Do you actually want Table B to be the parent table in your application so that Table can inherit (Look Up) fields from Table B?
The architectural choice is dependent on the business process rule.
So assuming that you have something like Customers and Orders as the two tables. The typical arrangement is to say that Customers are the parent table and Orders is the child table. Your external integration might bring over new order records every week that have to be related to the parent Customer table. In the Customer Table you can create Summary Fields to tell you things like total revenue for the week from the Orders records.
Does this help or is your question about different issue?
------------------------------
Don Larson
Paasporter
Westlake OH
------------------------------