FoxPro index problems with Access

[jdola]

I have a customer that is using Access to create reports from FoxPro
tables. We started noticing problems with the indexes on the FoxPro
tables. It is to the point where we have to delete and rebuild the
indexes on a nightly basis. We cannot determine if Access is the
culprit and I have not been able to look at the Access reports and
determine how he is linking to the tables. I realize this is not much
to go on, but does anyone see any possible problems that might result
from linking Access to FoxPro tables? Any suggestions would be greatly
appreciated. Thanks.

[Bob Quintal]

jd*********@appliedsystems.com (jdola) wrote in
news:3e**************************@posting.google.c om:

I have a customer that is using Access to create reports from
FoxPro tables. We started noticing problems with the indexes
on the FoxPro tables. It is to the point where we have to
delete and rebuild the indexes on a nightly basis. We cannot
determine if Access is the culprit and I have not been able to
look at the Access reports and determine how he is linking to
the tables. I realize this is not much to go on, but does
anyone see any possible problems that might result from
linking Access to FoxPro tables? Any suggestions would be
greatly appreciated. Thanks.

I have several Foxpro tables that I read from Access. Compound
indexes (.cdx) files are not subject to any issues due to linking
from Access in my experience, but .idx or .ndx files are subject to
all sorts of little problems, like the developer failing to
maintain them, users failing to open them.