I've received this error before. I'm not quite sure what causes it. A quick search using Google seems to imply that some part of the table's definition has changed - such as an index being dropped, or a temp table was dropped after a cursor was created.

Did you add the references constraint while the query was running?

-Mike

>SQL 7.0 SP3 Win2000 sp3.
>
>Today I got this error again...
>
>Could not complete cursor operation because the table schema changed after the cursor was declared...
>=====
>1. I just added a foreign key on a table X.
>2. When I run an SQL statement in QA no error.
>3. But when I run an SQL statement in my VB program I got that error using my login USR20. I used a RDO connection.
>
>Do you have an idea why ???
>
>Thank in advance.
>
>Dave
>Technologies Nter.