I'm glad to tell you that I wrote to Microsoft's people and they told me that it seems to be a bug in VFP8. Hopefully this will be fixed in SP1.

>>Hi! Thanks for your comment, well I don't agree with you because I test this one DBC well and it should give errors when using VALIDATE DATABASE what surprised me was the fact that VFP8 didn't recognize it and VFP6 did, but besides that VFP6 even could fix it and after that VFP6 and VFP8 showed that the DBC was ok
>>
>
>Hi Luis,
>
>What is it you don't agree about? Did you run my code? What result did you get? How this scenario is different from what you were doing to made DBC invalid? Please, give me something specific: a repro code, a DBC + tables for download or, if it is relatively small (zip less than 1Mb), zip it and send on my e-mal. Otherwise, this is not going anywhere.
>
>Thanks,
>Aleksey.
>
>>
>>
>>>>Hi Friends:
>>>>
>>>>This message is so that another bug in VFP8 that I found be taken into account for fixing it in SP1:
>>>>
>>>>I was just migrating one application from VFP6 to VFP8, the DBC only contains native VFP tables and local views, besides that, I had to change the length of some character fields and also the type of other fields. I did that, forgetting to update the respective views, I later remembered that I had to update the views. So, I decided to use VALIDATE DATABASE to help me fix those views, when I entered VALIDATE DATABASE it showed that everything is OK that made me doubt because I certainly thought that this command will reveal several errors, then I thought I'd have to use VALIDATE DATABASE RECOVER so that it recognize the errors and fixes them, to my big surprise, the DBC was ok for VFP8. So, I tried to validate the DBC in VFP6 and it DID recognize the errors in the views, then I used VALIDATE DATABASE RECOVER and VFP6 flawlessly fixed those errors. I thought VFP8 didn't have these kind of bugs. I remember having read that VFP8 was the most stable version ever released. Hmm, that make
>>me
>>>>think not to migrate my applications and wait until these errors and others that I guess exist be fixed in SP1.
>>>>
>>>>I have available the "problematic" .DBC so that anyone would want to have it I'll send it so that this be fixed in SP1.
>>>>
>>>>I hope this can help so that VFP continues to be the greatest development environment I know and I love. Thank you for your time.
>>>>
>>>>Sincerely,
>>>>
>>>>Luis Guerra
>>>>lguerra2@yahoo.com
>>>
>>>Hi Luis,
>>>
>>>If I run the following code in VFP6,VFP7 and VFP8, the result is the same 'Database container is valid.' It is more likely that VFP8 changed DBC and made it invalid for VFP6, but DBC was valid VFP8 DBC.
>>>
>>>

>>>CLOSE DATABASES all
>>>CLEAR
>>>
>>>DELETE DATABASE dbctest DELETETABLES
>>>
>>>CREATE DATABASE dbctest
>>>CREATE TABLE dbctest (f1 C(5))
>>>
>>>CREATE SQL VIEW testview as select * from dbctest
>>>
>>>ALTER TABLE dbctest ALTER COLUMN f1 c(10)
>>>
>>>VALIDATE DATABASE
>>>
>>>ALTER TABLE dbctest ADD COLUMN f2 c(2)
>>>
>>>VALIDATE DATABASE
>>>
>>>return
>>>

>>>
>>>Thanks,
>>>Aleksey.