>Robert, please clarify.
>
>-- So you have switch to 1.9.6
Not quite. As you read in the other email, I can't get 1.9.6 vxmcd
working for me yet. But I will switch if only to get proper support
from you. This is mission-critical project for me and the current
trouble really spoiled my reputation here.
>-- you have create in 1.9.6 totally new fresh db
>Or you have open old db with corruption on 1.9.6 and it was fixed ?
I created the db with 1.8.10 anew from text files.
I placed this GOOD FRESH db on the server for users to use.
After a few hours, users started reporting 351 errors.
I block user access to two corrupted fields
but after a while another gets corrupted.
There was no crash or any other trouble that I know of.
The VarChars that got corrupted now are different than earlier.
>-- now in 1.9.6 db you have made diagnose, no problems ?
>
When I open (a copy of) that corrupted db in Vapp 1.9.6 I get clean
health report, but as you pointed out, since VarChar format has
changed, all VarCHar fields are somehow modified when opened by 1.9.6
and that probably eliminates the corruption. So does cloning.
I have been using this db in this setup for half a year with no such
troubles, so there is something that I did lately that causes it
somehow. But what?
Robert
©2002 Robert Brenstein |
