>Now I believe that INDEXSEEK works for both table and view as I realized that my Treeview display was working before I got this error.
>
>I have made some trial and error testings and I found out something. I still don't know how to fix the problem and I will greatly appreciate if somebody can help me on this.
>
>I debug the code and displayed the values before INDEXSEEK. Everything is correct; the unique key is correct, tag name is correct and my view is 'v_example'. I found that I am getting this error when my view is ordered by the unique key (my unique field is in "Order by" tab). However, if I removed this key in the 'Order by' tab, my error is "Element not found" as my Treeview data is being loaded. The error is caused by my child node coming first before my parent node. And I am not surprised because they are not sorted according to the unique key.

I recommend creating an index on the view as mentioned in the Mere Mortals Developer's Guide topic "Creating Indexes on Views".

Regards,