Updating a recordset

Posted by / 27-Apr-2018 15:43

Updating a recordset

-- PRB: Oracle Servers Convert Empty Strings to NULL The information in this article applies to: Active X Data Objects (ADO), versions 1.5, 2.0, 2.01, 2.1, 2.1 SP2, 2.5 SYMPTOMS The Visual Basic Run-time error 80040e38, which follows, occurs when updating a record containing a variable-length string field previously set to the empty string: The specified row could not be located for updating; Some values may have been changed since it was last read. Close Set rst = Nothing Set cnn = Nothing The simplest work around for this problem is to use the Resync method on the recordset object as illustrated by this code example: Dim cnn As ADODB. Execute "INSERT INTO mytable VALUES (100,'value')" Set rst = New ADODB. CAUSE When setting a field to the empty string, Oracle servers automatically convert the empty string to NULL, but the object requesting the edit is not notified.

Microsoft Office Access 2007 provides a number of tools for updating existing records, including datasheets, forms, queries, find-and-replace, and the new Data Collection feature.I have an ADO Recordset, and i'm trying to edit a record in it. Some values may have been changed since it was last read and the solution was to use resynch Hi Azra Sound, I assume that you know ADO :-) If yes, you certainly run already into the nice thing that ADO raises many errors, but with the same error number.The problem is that when I try to edit a newly added record I receive this error message: Run-time error'-2147217864 (80040e38)': The specified row could not be located for updating: Some values may have been changed since it was last read. Even the error text is sometimes the same grrrr More even, the error text is depending on same language settings, wich makes it difficult to simply analyse the Err. (developer's) life would be too easy, and our income too low :-) its now in the "answered section" the accepted answer was the exact post the wsh2 has on this question..a matter of fact, upon seeing the question i simply posted a link over to this question for the questioner to reference...i believe the question was named ".qid=20100781 I'll leave this question open for a little while longer in case someone comes up with a faster cloning solution that will allow me to update, but I'm not holding my breath :-) Regards GK Thanks bhess1 - I'll try that next week.I've reverted to my own clone routine and by getting the data using Get Rows before populating my clone I've got the time down to 10 seconds for 6000 rows.

updating a recordset-48updating a recordset-19updating a recordset-10

If there are no records, the BOF and EOF property are True.