Index corruption - Clipper

hi,

>Does opening database with READONLY option affects on decrease of
>index corruption cases ?

sample ?

greetings by OHR
Jimmy

Milomir

> Does opening database with READONLY option affects on decrease of index
> corruption cases ?

If you open the DBF readonly then the indices are also opened readonly.
You CANNOT update any DBF/INDEX if it's open readonly - so there is no chance of
corruption.

IIRC if you try you'll end up at the DOS prompt (if you don't have an error
handler in place that is<g>)

HTH
Steve

Thanks Steve, I think that's the right answer.
The same application on the some places reports index corruption on about
one or two weeks. On the other places everything is OK. I'll try with
opening DBF's via READONLY on every place in program that does not changes
DBF.

Milomir

> I'll try with opening DBF's via READONLY on every place in program that does
> not changes DBF.

You won't be able create new or temporary indices if you open DBFs readonly
either.

HTH
Steve

hi,

>The same application on the some places reports index corruption on
>about one or two weeks. On the other places everything is OK. I'll try with
>opening DBF's via READONLY on every place in program that does not
>changes DBF.

did you allways open DBF with all Index files ?
did your Index file have the same Date/Time stamp ?

greetings by OHR
Jimmy

Try linking in CPMI.LIB
Is your file handle sufficient?. FILES=125

Benny