Re: -710 Error How to fix?

I've also faced the same problem. This error occurs usually when you drop and recreate(modify) an exiting stored procedure.Hope this gives you some pointers. The solution so far (according to my knowledge) is do not drop and recreate SPL when are around or run full update statistics after each modification!! Creating new SPL's with out dropping existing SPLS wont cause this error though. Rgds, Abhi Wolf P'ter wrote in message <3569B97E.754F3791@procent.hu>... >We using Online Dynamic Server v7.20 Workgroup Edition. >When some database modification required ( e.g. Adding new indexes, >foreign keys ) >which requires to exclusively lock a complete table or tables, but these >tables is in uses, the server respond sql error > -347 Could not open table for exclusive access. >Its correct, but when somebody wants to change some data in that table >gets the sql error > -710 Table table-name has been dropped, altered, or renamed. > >And this error infects other tables through foreign keys, like a virus. >Users get angry tying to post their modifications and getting -710 with >various table names. >I found only one solution: > Kicking out all users and running update statistics. >But its very time consuming ( about 1 hour ) > >How can I query which tables are infected by -710 "virus" to run update >statistics for only that tables? >Or how can I prevent getting -710 when I need some modification in a >litte part of my database and not want to kill all my users? > >Has somebody any idea? > > > >