>Finally got it. The problem had nothing to do with SQL too long or SYS(3055). For some reason when I inserted a new record into the local view, the record was showing up in the base table immediately [no tableupdate was ever issued]. Well, in the base table, the default value for the KeyID field was firing and setting the KeyID value to the next integer value. Well the view still has the KeyID as 0 [I do not carry over the default value for the PK in the view].
>
>To work around this, I had to retrieve the next value for the KeyID and include this value in the Insert Into command so the view and the table would have the same KeyID value. Looks to me like the Create SQL View command needs a NoFilter clause option.

Hmmm, that automatic update is strange. You're thinking you got a filtered table, I gather -- I didn't think that was possible. Must be some other explanation, but don't ask me what it is. Anyway, we'll consider sys(3055) to be back in good graces.