Ah, that's different. Unfortunately the driver fails miserably (ie the
subscript error) if you try to do multiple queries on the same
connection. Maintainers past (Colin?) have suggested that it can work
if, for example the resultset is completely read before another query
but I do not rely on it at all. It is ugly to have to open multiple
connections but try it to see if this explains your problem. Also be
very careful to ensure[connection close] after using one because if
you dont clean up, eventually the server will refuse connections (eg
100 limit).

You might also want to look at my Persistence package which is an
object to database mapper in which I try to work around the limitation
above. (BTW, if anyone is interested, my latest (as yet unreleased)
version has good support for mysql replication by allowing all write
operations (insert,update etc) to be sent to a separate master server,
and by allowing object registries to be isolated using
DynamicBindings.

-- Alan

> I sincerely apologize for my previous post, but apparently the code I
> posted before (which was a snippet of the actual code) does work. The
> exact code that I was trying to execute (which does generate the
> exception mentioned) is: