.NET 2.0: iAnywhere.Data.UltraLite
Win Mob 6 (CE 5.2.1946)

We are having the same issue as Phil was having ("Too many
temporary tables in connection") in this post:

We have made sure all readers/resultsets are explicitly
calling Close() inside of their respective using blocks as
Tim McClements suggests.

In this post Chris Keating (December 19, 2011 3:01 PM) said
that he was able to repro the issue and that he would

But I don't believe there was any response from him after
that. So is this an acknowledged issue? Other than upgrade
from 10.0.1 to 12.0.1, we haven't touched any query-related
code and now it's "broken". Looking in "SQL Anywhere Bug
Fix Readme for Version 12.0.1" I couldn't find anything that
suggested it might have been addressed. Why does it break
going from v10 to v12 and is adding appropriate indexing the
only way to fix this? Is there a way to increase the
connection's temporary table limit?