If the index are needed for a search, then leave it there. Removing them and using a LOCATE instead of a SEEK will slow down your app. There is a small penality to take when inserting a new record, because the index need to be updated, but it's quite small.

I don't experience many problems with the CDX. Make sure that the PC where the database is have a UPS and that the user don't quit your application with the 3 fingers salute. A 3-party tool like Stonefield Database Toolkit can help also.

HTH

---

>I posted a message "Help!...Records Inserted into the table competely lost.." a little while ago relating to this question
>but I want to ask another related question:
>
>How many indexes it too many?
>The table has 8 out of its 16 columns indexed and only has insert activity in it no deleted, updates.
>
>Is this a performance problem or potential problem here.
>I know about Oracle as a DBA and I would deffinetly
>critize this number of indexes on a table of this type for insert performance but I have found foxpro indexes to be extremely unstable.
>I often have to drop the cdx file and reindex twice a week on this table.
>
>Problem is all the foxpro code does stuff like.
>set order to tag blah
>seek blahblah
>
>Is this a/the problem???