It seems to be the quantity of records.

If I move the TABLEUPDATE command and update each line, one by one, all lines are updated successfully (including the 9th line).

If I have the view with 8 records in it, the tableupdate works for the entire view if I update the table normally (all records at the same time).
If I have the view with 9 records in it, the tableupdate fails for the entire view if I update the table normally (all records at the same time).

By the way, these are new records going into SQL Server...not an update of existing records.


>Rick,
>
>This is very strange, indeed. Are you saying you can update any 8 records but 9 always fails? Or is it always the same 9th record that causes a problem? Maybe there's something about that 9th record, although I can't think of what that might be. If you come up with any more information that might be relevant let me know. I see that Michael Levy has been on this thread as well. Maybe he'll have a thought. I'm definitely stumped.
>
>>The value of AERROR() is as follows:
>>Test(1) N 1526
>>Test(2) C Connectivity error Microsoft ODBC SQL Server Driver Invalid pararmeter number
>>Test(3) C Microsoft ODBC SQL Server Driver Invalid parameter number
>>Test(4) C S1093
>>Test(5) N 0
>>Test(6) N 1
>>Test(7) C
>>
>>The SQL Line from the View is:
>>SELECT * ;
>>FROM dbo.arshipline Arshipline;
>>WHERE Arshipline.rol_rohfk = ?lcrol_rohfk
>>
>>Other important stuff from the view:
>>Key and Modified Fields is selected
>>SQL Update is selected
>>Send SQL Updates is selected
>>Key Field is rol_pk
>>Timestamp is not selected for update
>>
>>Remember that it works if I am updating 8 records.
>>It fails if I am updating 9 records.
>>All records are identical except for the rol_pk field.
>>The value of the rohfk is the same for all 9 records.