Your right about the lesson in communication. Actually, it was a suprise new server. More than an hour was spent figuring out who was responsible for the change. Part of the fun of working in a large organization.

I don't think they looked at what was there. Then when we tried to move back to the old server, the brought the new limits back with them so it didn't work in the old environment either.
Anyway, all seems to to well now. Might even do some programming today <g>.

>>Thanks for the reply. Turns out it wasn't a version problem. The problem was that when the folks who handled the migration to the new server restricted the users to limited disk space. The limits were to low and indexes were becoming corrupted, causing errors, killing Fox...tables not closed...etc.
>>
>>
>(snip)
>
>Bummer! Good lesson in the need for communications between the developers and the network weenies... Seems the network guys should have at least **asked** for guidance. Didn't they look at what was there, or did you expand the disk space requirements later without knowing about the limitations put down?
>
>Anyhow. Thanx for following up.
>
>Rob