We have an app that runs various stored procedures correctly (all be it slowly) We have turned on ODBC connection pooling and the stored procedures now seem to "remember" previous parameters. This is obviously a result of connection pooling which has given us significant speed increases but unfortunatly whilst this error exists with previous parameters being re-used we cant put it live.

Any ideas why the parameters are being "remembered" ??