>Hi,
>
>Thank for your advise. Most of the time, my client server
>just hang up for reason not know to me, which my program
>and data files are reside on which are causing all the
>CDX files to be corrupted.
>
>Could you kindly explain in more detail on
>'putting the table and cdx on the readonly server plus
>non-structure index and more coding alternatives.'
>I like to know of better or alternative ways to
>solve indexes problems.
>Any advise is very much appreciated. Thank you.

Sure...but note that this only is valid where tables/indexes are not altered at runtime:

For multi-user app DBs, I keep two basic directories, one has server access for users set to read/write (call this PUBLIC), and one is readonly (call this PRIVATE). I put everything that does not require user updates into the readonly directory PRIVATE. PRIVATE contains all DBCs, all lookup tables and indexes, and I suppose you can even have IDX or CDX on editable tables on fields that are not updateable, if records are not added/deleted, in theory (though I haven't actually done this, since I usually just use views and cursors with temporary indexes...

The idea is anything kept readonly is less vulnerable to corruption (as well as possible users trying to hack into things). The large lookup tables are especially vulnerable to index corruption, and I've had no problems after making tables/indexes readonly.