V4MD - Error -39

Roland Hildebrandt r.hildebrandt at sbt.fr
Thu Sep 9 11:15:40 CDT 2004


> >>> I need to understand why we become this error on all accounts
databases
> >>> after 6 months of work.
> >>>
> >> This could be sys/app crash
> >>
> >
> > I don't think so as far as we get the same problem on 20 computers in
one
> > week. And I can redo the bug again and again using the way I explained
in the
> > last mail.
>
> You can reproduce?

Yes of course, I've got a test project with only 10 lines of code using a
set of non crypted DBs which are said all rigth by diagnose but using the
code I allways become -39. I can send it if you want.


> > So the problem seems to be linked to the state of the DB. The
> > problem is to understand why the DB goes in this bad state after 6
months of
> > use.
>
> Only on db which is old 6 months

Yes, with a clean one there is no problem. And they were no problems during
6 months.

> Roland, first of all I will recommend switch to Valentina 1.10
> It have many fixed bugs. Because no big sense discuss 1.9.8,
> May be that bug is fixed in 1.10.

I made my tests with 1.10 / 1.9.8 there are no changes (still using the DB
generated and used 6 months with 1.9.8).


> >>> In fact we have to make the same kind of project for october. So I
have a
> >>> big problem because I know I will lose all data after six months on
one of
> >>> the database but I don't know why and I have no workaround.
> >>>
> >>> That's why it's important for me to understand why this happens.
> >>>
> >> You should make sure that you have as many flushes as possible.
> >> This reduce chance of corruption.
> >
> > Accounts is the only DB we change during execution. We use flush command
on
> > this DB in each script (not each function, but at the end of the script)
> > which updates it.
>
> ok
>
> > This raise me another question : Our other DBs are read only but i have
been
> > surprised that the files (vdb, ind, dat, blb) changes even if not
updated. I
> > have seen this using CVS : I open the DB make a read only request on it
then
> > close DB. After this the file is 'modified' in CVS. What's reason for
this ?
> > Is it linked with some indexes or optimisation for following request ?
>
> Hmm.
>
> IF files marked as READ ONLY by OS, then any app and Valentina also
> cannot modify that files.
>
> So I wonder on your words.

The files are not marked read only by OS. But we only made open, read only
requests, close, on these DBs. No alter, insert, delete, update on the data
or structure. Could they change this way ?

Best regards

Roland Hildebrandt




More information about the Valentina mailing list