I'm having a problem with VFPOLEDB on an ASP web site that was just set up this last week. I can't figure out what's wrong with the settings, because it seems to be set up in an identical configuration to a server from two weeks earlier.

Essentially, an ADO recordset from a VFP table using OLEDB gets created as expected, and it can be read, but when I go to write the changes back to the table I get an error.

If anyone has ideas about what to look for, I'm all ears. This configuration works fine when I change the connection string from OLEDB to ODBC. It also works fine on the other server.

There does not seem to be a permissions problem. I turned on security auditing on all drives and re-ran my test case, and had no security failures. It is also not related to a date field. I pared the update down to a single, plain vanilla text field and still got the error.

The complete text of the error message is:

Microsoft Cursor Engine '80040e21'

Multiple-step operation generated errors. Check each status value.

Testpage.asp, line 263

The line of VBScript code in the ASP page which failed is:

Call mrcrTest.Update()

The connection string being used is:

"Provider=vfpoledb.1;Data Source=\\testserver\data\;Collating Sequence=machine"

This is plain vanilla ASP using a VFPOLEDB object to connect to a set of VFP6 free tables. This same code and connection string is working in on our production server right now. The operating system is Win2K.

It works fine to READ the contents of the tables. What it won't do is UPDATE them. It is the test server that is having problems. If anyone has seen this message before, please let me know.