|
It might be the RDBCNNMTH setting (SET OPTION statement). If the default setting has changed from *RUW to *DUW, it might account for this behavior. I've seen that message before when I tried to create a cursor under *DUW (Distributed Unit of Work), even though I had explicitly closed it. I believe it is a result of SQL trying to intelligently cache objects that are expensive to create. If that is actually the problem, it might be worth investigating how to set the parameter values in order to reuse the existing cursor. hth Pete >From: "Adam Lang" <aalang@rutgersinsurance.com> >To: <midrange-l@midrange.com> >Sent: Thursday, August 29, 2002 8:22 AM >Subject: Re: Cursor C1 already open > > > > I was doing the explicit close in both my attempts. I even set the > > > recordset to nothing after the close. > > > > > > It only works if I set the connection object to nothing also and >reconnect > > > on every loop. > > > > > > I am reinstalling CAE 4.4 and seeing if it works. > > > Pete Hall pbhall@ameritech.net http://www.ameritech.net/users/pbhall/index.html
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.