>After all these years with Fox We are still having problem with table corruptions. We have remote installations of our applications and we get a lot of table does not match with Index errors.

Yes, it's a problem we all seem to live with. I do understand the difficulties involved with updating the same file from multiple workstations, so I give the VFP team some slack in this regard. I think it's just the nature of the beast when you're dealing with file system based databases.

There are ways we can insulate ourselves from this though:

1. Use a multi-tiered application architecture. Having a middle tier component that accesses the date files (preferably running on the same system that has the data files),instead of the workstations will reduce any network related corruption. And a side benefit is that you'll be able to run your app across a WAN.

2. Have a pristine network with the proper workstation settings (no file caching etc...). This is hard for us to control, but if you have an optimal network and workstations, you should have good data.

I don't know of a utility that allows dynamic index file rebuilds without having exlusive access to the table, but you could institute a nightly index rebuild if your app availability requirements allows it. This would at least fix any problems that happened that day.

HTH.