snip here...

Most of our projects ( Insurance, Hospital, Dutyfree Shops ) were done purely Visual Foxpro - as the Tool and Database. And tables have huge Indexes including Filtered indexes. One table have 60 indexes and still we do not encounter problems just like yours. One thing we required to our client is that SERVER should be secured to any technical problems so that tables and indexes will not be corrupted. In a network environment, corruption of files (dbf & cdx alike) are seldom to happen.

>Hi!
>
>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???