I am getting an SQL error when I try and execute a TABLE that is a child of a table in another local database. In this example I am linking to Contacts from my SugarCRM database via a FABRIK connection. The problem is that the generated code does not qualify the foreign fields correctly, assuming there are in the local database. They aren't. Solution 1).. Local view to be used. I have a local view (TABLE linked into the Parent table), this works. I was expecting to be able to define my foreign key element back through my local Fabrik Table VIEW), but this table does not show during the definition of the foreign key on the child table, under the local database option. Forcing me to point it directly into the original Parent table (using the other CONNECTION). Under this option the view specific qualification should be used, as Fabrik and the user would consider that this is local link. Solution 2)... Point back to original Connected.Table Under the current set-up I would continue to CONNECT back to the original TABLE, but the generated SQL must better qualify the ELEMENT, using the CONNECTION.TABLE.ELEMENT structure. I know what everyone is thinking... Bad idea to connect 2 tables from 2 different databases. But the benefits of no duplicated data, is a far better solution. Especially if the data can be filtered etc. (which I believe is currently possible). Letting SugarCRM handle the contact functions for a Customer, and the FABRIK system handling other back-end data functions against that person. But the person is defined only once, 1 phone number, 1 address etc. PS. It was a great feeling to get the VIEW into SugarCRM working, we are so close to getting this working, if this little bug can fixed.