How are you getting the sql data into your VFP app? Are you using remote views? If that's the case make sure your VFP DBC is valid. Another thought - perhaps the SQL user rights have a problem??

As far as the SQL indexing problem - I've been lucky to of never encountered such a problem myself so I really dunno - hopefully someone else out here can assist....


>Hello,
>
>I reindexed each table in the database; however, the problem still exists. When I get to a certain point in the program and try to add a record to a specific child table, I get a message that I can not add a new row. Also, when I run a command to gather information and populate another table, I error out. It is interesting to me that I can start a new case, add a record and not get a error. I can add a child record to that case record and no error; however, when I try to add a child record to that table, I get the error.
>
>I am able to go into the SQL database and browse each of the tables - including the table that I believe has a problem. I can run queries on the tables too. It is just when I try to add a record to this particular table that the error occurs.
>
>How do I determine if a table is corrupt? How do I determine if a record in a table is corrupt? Is there a way to repair a table other than just doing a DBCC REINDEX?
>
>Thanks,
>
>TFISHER
>
>
>>This might help....
>>http://msdn.microsoft.com/en-us/library/aa258828(SQL.80).aspx
>>
>>>Hello,
>>>
>>>I have a VFP front end and a SQL 2000 backend. The server the SQL is on has a bad disk and started throwing IO errors (RAID 5 - the bad disk has now been replaced). About that same time, the VFP application that had been working just fine for several years, started crashing when a new record was added to one of the tables. I can add records to some of the tables; however, when I get to a certain point and try to add a record to a specific child table, the program errors and says that it cannot add a new record from a view.
>>>
>>>Interestingly enough, I did a backup of the SQL database and put it on my SQL 2008 and it runs just fine.
>>>
>>>At one point, I believe I saw a message about sysindex table.
>>>
>>>How can I troubleshoot the SQL 2000 database and perhaps re-index and fix the bad table(s)?
>>>
>>>Thanks,
>>>
>>>TFISHER