>By damaged index, do you mean SQL Server index? The only index on it is the PK which is an integer and clustered. The only way I can drop it and recreate it is to drop the table (I believe) and recreate it. I might end up trying that. Other than that, no other views, etc. with that name.

Ooops, should have read your message more carefully. I figure there's no way Fox would know if/when a SQL server index may be damaged, so the message looks really strange. You could suspend at the error, and issue a Aerror(aErrArr) to gather the extended error information, and maybe conclude something from that.

There still remains a possibility that there's a .cdx or .idx file with the same name as your view (or its alias, if different) somewhere along the Fox's path. It may try to update it, thinking it belongs to your view, and then discover the key expressions have nothing to do with your view. Check for any file called myremoteview.cdx or .idx - and if it's there, try to name your view differently.