Re: 'Not an Updatable Set' problem with OOLE

In article <48da3f$afm_at_tcsi.tcs.com>, Murthy Jarugumilli <murthy_at_tcs.com> wrote:
>Hi All
>
>We are using the OOLE 1.0.55 data controls in the place of the standard VB
>data control in many of our applications. We connect to Oracle 7.1.4 on HP
>server in the backend.
>The problem we are having in one of the front applications is that, at random
>times, a normal SELECT query with some simple join condition (positively,
>without 'SELECT FOR UPDATE's) comes back with an OLE automation error 4117.
Are you absolutely sure it's random? OO4O doesn't do much with the query other than pass it to Oracle to parse,etc. A Movefirst doesn't cause records to be updated, just the current record to be moved. If it truly is random, maybe you're seeing some other bug that effects this feature.

>This error does not occur when we set the RecordSource property of the data
>control to the SQL string and Refresh. This error occurs when we do a
>dbMoveFirst or dbMoveNext after refresh. The 4117 error is supposed to come
>when we attempt to make an update on a non-updatable set. In our case, we
>clearly are not attempting to make an update, 'cause we are not trying to
>change
>any fields in the record set. The data control handles simple two table join
>queries.
>
>I could be missing something here. Any thoughts are welcome.
>
>Thanks in advance
>
>Murthy Jarugumilli
>murthy_at_tcs.com
>TCSI.
>
Received on Thu Nov 16 1995 - 00:00:00 CET