Devart Forums

Hello, Alix, There is a funny question.We tasted a characteristic of ODAC, that is, in every table(dataset), we built a lookup field for a foreign key, e.g.,In table EMP, a lookup field named EMPQueryDEPTNO was built for the foreign key DEPTNO, we did this to aim that a combobox appear automatically for the foreign key in the column in grid of our project. We did enjoy the advantage of this characteristic , because it really acts. Unfortunately, when we upgraded odac higher from 5.55.1.23, we suffered from this, the dataset with foreign keys could not be opened quickly, very slow, intolerably slow, even eat up all the virtual memory, made the machine dead, we cannot suffer any longer, and had to degrade to 5.55.1.23. we wonder what happened to newer edition. What could we do to change this now? Please help us.


Best Regards
pengpeng

Please send to ODAC support address complete sample that demonstrates your problem and include script to create server objects.

Umm, the sample is too large to be sent here. We build a lookup field in every TSmartQuery for a foreign key in the concerned Oracle TABLE which the TSmartQuery points to. The characteristic help us a lot, while puzzle us a lot.