SanjayK wrote:
It was indeed a problem related to prepared statements. It turned out to be less work than I imagined. Just before creating the new table, I finalize all the prepared statements by calling a methd and after creating, I prepare them again. This solved the problem. But I am puzzled as to why the prepared statements should be affected if an unrelated new table is created.
I believe that the rule is that if the db schema changes, prepared statements become invalid.
HTH, Gerry
