I just had a play with this. The order of the tables aren't that important if only one of them have small objects.

But the order of the conditions in the *Where* field must reflect the order of the tables in the *From Tables* field.

I tried joining four tables. One with spatial data called POLYGON. And three with alfanumerical data only called M, K and M_K.

These two queries give the same result:

1:

*Select * from POLYGON, M, K, M_K *

*Where POLYGON.KOMKODE = M.KOMKODE *

*And M.KOMKODE = K.KOMKODE *

*And K.KOMKODE = M_K.KOMKODE *

*into Selection*

2:

*Select * from M, POLYGON, K, M_K *

*Where M.KOMKODE = POLYGON.KOMKODE *

*And POLYGON.KOMKODE = K.KOMKODE *

*And K.KOMKODE = M_K.KOMKODE *

*into Selection*

Notice how the order of the tables in the From part is similar to the order int he Where part

But this one fails:

*Select * from POLYGON, M, K, M_K *

*Where M.KOMKODE = POLYGON.KOMKODE *

*And POLYGON.KOMKODE = K.KOMKODE *

*And K.KOMKODE = M_K.KOMKODE *

*into Selection*

Notice how the order doesn't match. POLYGON is first in the *From Tables* but second in the *Where* part.

This will raise this error:

So in theory, you can add additional tables to the statement as long as you are able to join the new table to the previous table.