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