Column is not found

I've found a resolution to this problem, or at least a resolution for the
defined database. In the FOR/NEXT loop where the recordset fields are
replaced by array contents, I added an IF statement that causes the recordset
field to be changed only if the field and array content are different, i.e.
only if something has changed as a result of the processing. Code:

FOR i = 0 to 74
IF rs1.Fields(i) <> PlyrArray(i) THEN
rs1.Fields(i) = PlyrArray(i)
END IF
NEXT i

I'm not sure why this works, except perhaps that fewer "resources" are used
for the more limited replacements -- any other ideas? Also, I'm not sure if
the resolution will be effective with larger databases.

Finally, let me say that many of Microsoft's error messages are very poor,
e.g. what are the causes of the error message I got? Further, I spent many
hours in many parts of the Microsoft website (e.g. VB, FoxPro, Databases, XP,
etc.), and in several website forums, and did not find a single specific
reference to the "SQL: Column 'Q.....' is not found" error message. How can
that be?!

"TomB" wrote:

 > Some additional information:
 >
 > -- In case anyone is wondering, I go through all the database records via DO
 > WHILE NOT rs1.EOF. The For loop and rs1.Update in the original post is
 > within the DO WHILE/LOOP, within which I also do rs1.MoveNext
 >
 > -- I read somewhere in another post that Move Next automatically updates the
 > recordset. Therefore, I removed the rs1.Update statement, leaving only the
 > rs1.MoveNext statement. I got the same error near the end of the processing.
 >
 > "TomB" wrote:
 >
  > > I am using the ODBC Visual FoxPro Driver in a VB application. One part of
  > > the app processes a database of approximately 500 records with 74 fields in
  > > each record (each record is approximately 2500 bytes), collects new
  > > information for the fields in an array, and updates each record as it goes,
  > > i.e.:
  > >
  > > For i = 0 to 74
  > > rs1.Fields(i) = PlyrArray(i)
  > > Next i
  > > rs1.Update
  > >
  > > I can successfully process a designated subset of the database (about 125
  > > records), but when I attempt to process the complete database (or a large
  > > subset of it), I get the following error on the rs1.Update statement:
  > >
  > > Error '-2147217900(80040e14)'':
  > > [Microsoft]ODBC Visual FoxPro Driver SQL: Column 'Q........' is not found
  > >
  > > In different runs I can get different contents in the 'Q........'
  > > information, e.g. Q727P38, Q705P125, Q707P94, etc.
  > >
  > > It would seem as though there's some kind of a memory or temporary file
  > > constraint (?). I have tried with BackgoundFetch=No in the connection
  > > string, nut the problem still occurs.
  > >
  > > Does anyone have a solution?
  > > --
  > > Tom Buggy<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Column is not found 

Where are all the vaunted Microsoft MVPs and/or FoxPro/VB developers with an
explanation of how/why this problem occurs?

"TomB" wrote:

 > I've found a resolution to this problem, or at least a resolution for the
 > defined database. In the FOR/NEXT loop where the recordset fields are
 > replaced by array contents, I added an IF statement that causes the recordset
 > field to be changed only if the field and array content are different, i.e.
 > only if something has changed as a result of the processing. Code:
 >
 > FOR i = 0 to 74
 > IF rs1.Fields(i) <> PlyrArray(i) THEN
 > rs1.Fields(i) = PlyrArray(i)
 > END IF
 > NEXT i
 >
 > I'm not sure why this works, except perhaps that fewer "resources" are used
 > for the more limited replacements -- any other ideas? Also, I'm not sure if
 > the resolution will be effective with larger databases.
 >
 > Finally, let me say that many of Microsoft's error messages are very poor,
 > e.g. what are the causes of the error message I got? Further, I spent many
 > hours in many parts of the Microsoft website (e.g. VB, FoxPro, Databases, XP,
 > etc.), and in several website forums, and did not find a single specific
 > reference to the "SQL: Column 'Q.....' is not found" error message. How can
 > that be?!
 >
 > "TomB" wrote:
 >
  > > Some additional information:
  > >
  > > -- In case anyone is wondering, I go through all the database records via DO
  > > WHILE NOT rs1.EOF. The For loop and rs1.Update in the original post is
  > > within the DO WHILE/LOOP, within which I also do rs1.MoveNext
  > >
  > > -- I read somewhere in another post that Move Next automatically updates the
  > > recordset. Therefore, I removed the rs1.Update statement, leaving only the
  > > rs1.MoveNext statement. I got the same error near the end of the processing.
  > >
  > > "TomB" wrote:
  > >
   > > > I am using the ODBC Visual FoxPro Driver in a VB application. One part of
   > > > the app processes a database of approximately 500 records with 74 fields in
   > > > each record (each record is approximately 2500 bytes), collects new
   > > > information for the fields in an array, and updates each record as it goes,
   > > > i.e.:
   > > >
   > > > For i = 0 to 74
   > > > rs1.Fields(i) = PlyrArray(i)
   > > > Next i
   > > > rs1.Update
   > > >
   > > > I can successfully process a designated subset of the database (about 125
   > > > records), but when I attempt to process the complete database (or a large
   > > > subset of it), I get the following error on the rs1.Update statement:
   > > >
   > > > Error '-2147217900(80040e14)'':
   > > > [Microsoft]ODBC Visual FoxPro Driver SQL: Column 'Q........' is not found
   > > >
   > > > In different runs I can get different contents in the 'Q........'
   > > > information, e.g. Q727P38, Q705P125, Q707P94, etc.
   > > >
   > > > It would seem as though there's some kind of a memory or temporary file
   > > > constraint (?). I have tried with BackgoundFetch=No in the connection
   > > > string, nut the problem still occurs.
   > > >
   > > > Does anyone have a solution?
   > > > --
   > > > Tom Buggy<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Column is not found