Tried that as well. I just went with ADO and a CursorAdapter to get it to work. If I get time, I'll try to trace the SQL passed by the CA, but I am up against a deadline right now. I think the actual problem was a typo in one of the very long field names. So much for meaningful error messages. FWIW, the cursor created by the CA showed those data types to be logical.

>WAG, True/False ?
>
>>UPDATE: I have isolated the problem to the values I am passing to the Yes/No data type fields in the Access table. It does not like Y or N, nor 1 or 0. What values does this data type expect? TIA!
>>
>>UPDATE #2: Does not like .T./.F., YES/NO either
>>
>>Trying to update data in a MS Access 2003 MDB. I am getting the data from an Excel spreadsheet, no problems there. Here is my SQL command:

>>UPDATE PWS_Assessment SET
>> PWS_Phone = ?pcSysPhone,
>> Response_Testing_pH  = ?pcPh,
>> Response_Testing_FCl = ?pcFCl,
>> Response_Testing_TCl = ?pcTCl,
>> Response_Testing_Alk = ?pcAlk,
>> Response_Testing_Trb = ?pcTrb,
>> Additional_Notes     = ?pcComments
>>WHERE PWS_Number = ?pcPWSID
>>  AND Assessment_Date = ?pdStatusDate

>>All parameters are private variables. Here are the data types in the Access table:

>> PWS_Phone            (Text)
>> Response_Testing_pH  (Yes/No)
>> Response_Testing_FCl (Yes/No)
>> Response_Testing_TCl (Yes/No)
>> Response_Testing_Alk (Yes/No)
>> Response_Testing_Trb (Yes/No)
>> Additional_Notes     (Memo)

>>The values that I passing for the Yes/No fields are either Y or N. Here is my error message, that makes no sense to me:

>>1526
>>Connectivity error: [Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 13.
>>[Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 13.
>>07001
>>-3010
>>1
>>.NULL.

>>Why is it expection 13 parameters?