select ssd.scenario_code,*
from clive  
inner join category c on c.category_code = clive.category_code  
inner join scenario_detail s on s.period = clive.period 
inner join scenario_stream_detail ssd on
ssd.category_code = c.category_code and
ssd.period = clive.period and ssd.scenario_code = s.scenario_code
where s.scenario_code = 335;

---

 Comments and Workarounds

---

This bug is very difficult to explain, but it basically revolves around having interdependencies in joins that cause the join optimizer to reorder the joins in a way that causes incorrect execution. The workaround is to put the NOJOINOPTIMIZE clause at the end of the affected query.

---

 Resolution

---

Fixed Problem on 4/24/2006 in version 4.24 build 1

---

 Products Affected

---

DBISAM Additional Software and Utilities
DBISAM ODBC Client-Server
DBISAM ODBC Client-Server with Source
DBISAM ODBC Standard
DBISAM ODBC Standard with Source
DBISAM VCL Client-Server
DBISAM VCL Client-Server with Source
DBISAM VCL Standard
DBISAM VCL Standard with Source