Hi,

I think there's a bug within the SQL functionality when dealing with lookup columns.

I've got two tables with information on conferences and the talks that are given during these conferences:

• The table "conferences_list" contains all conferences (dates, location, website etc.).
• The table "conferences_contributions" contains details on the talks planned for these conferences (title of contribution, people involved, other details) PLUS the name of the corresponding conferences as a lookup column.

I can now do a SQL query which combines the two tables and consequently gives me a list with the conferences and all contributions planned for it. (This procedure spares me entering all conference details every time I add a contribution to a conference.) The query looks something like this:

SELECT conferences_list.Conference, conferences_contributions.Title_contribution

FROM conferences_list INNER JOIN conferences_contributions

ON conferences_list.Conference = conferences_contributions.Conference;

If I want to see all conferences, even those where no contribution is defined I *normally* can do that by LEFT JOIN

SELECT conferences_list.Conference, conferences_contributions.Title_contribution

FROM conferences_list LEFT JOIN conferences_contributions

ON conferences_list.Conference = conferences_contributions.Conference;

Which doesn't work at all but gives me a table with way too much records. Suppose I've got 12 entries in table "conferences_list" and 20 entries in "conferences_contributions", it will give me a table with 12 * 20 = 240 rows.

However, it works fine if the column "Conference" in table "Conferences_contributions" is not defined as a lookup column but as a simple text column. It seems that, when the lookup column is used, every talk belongs to *every* conference instead of only the one selected in the lookup column.

Can I or can you do something to make it work the way I want?

Thanks

John