Here's the problem: I have several TSQL stroed procs that use a cursor on the
same table that has 4 computed columns. I also have several processes that
call these stored procedures to retrieve rows from the table and build a
string that is put into another table. The problem I am having is an
occasional error message from ADO that the schema has changed since the
cursor was openned (0x80040E14). My question is this: Can two separate
connections accessing the same row in the table with computed columns cause a
schema change error? I should also mention that the computed columns are
values that are generated by .NET CLR user defined functions.