FOXPRO 2.6a

The "Not a table/DBF" occurs frequently on only one table over an NT4
network.
The table is large (300,000) records.
The table is not corrupt because if the user retries a few times the file is
eventually opened and the problem is intermittent.
Why does foxpro think the table is not valid. What could the network be
returning to the app that makes foxpro think the table is not valid?

Any ideas?

Thanks
Andrew Grandison

I'm wondering whether the table has sustained some damage-not enough to disable
it, but enough to cause trouble. You might want to try copying it over to a new
file, rebuilding its indexes and seeing if that doesn't clear things up. Zip up
the old files before you replace them as a precaution. I've seen intermittent
errors when too many try to access a table.
HTH
Mike Ballai

Try to check if your NT4 server is closing file connections when you stop using
them. Sometimes it does not. First sign is visible server slow down.