>Al,
>
>Could the fact that the users log into a domain rather than the old workgroup be relevant to the problem?

I'd say no - I can't think of any way it could be relevant.

>
>>>I've managed to finally get some info from the IT manager who keeps everything close to his chest.
>>>
>>>It turns out that the old server was running SAMBA, but the new one is not.
>>>
>>>He says a specialist from the server provider is monitoring the system tomorrow looking for any issues on network response times.
>>>
>>>The IT Manager says "At the moment it feels to me like there may be an intermittent delay which the Foxpro application cannot deal with"
>>>
>>>Is this feasable?
>>
>>What OS is the new server running?
>>
>>Bear in mind that Samba is not an OS - it's a process that runs on top of (typically) Linux, and emulates an SMB/CIFS file system to make the Linux box look like a Windows box to Windows client machines.
>>
>>Is the server still in the local office or has it been relocated to another office? If it's now at a remote location then yes, depending on the type of connection in place and other traffic on the link, there could be significant latency from time to time which Fox might interpret as being unable to open a file, or as a dropped connection.
>>
>>
>>>>>Hi
>>>>>
>>>>>I have an application that has been fine for months. Its essentialy a grid that shows the progress of all jobs going through the factory. Each row being a seperate job.
>>>>>
>>>>>The customer has revently upgraded the server to a SAMBA about a week ago (think thats right, I wasnt involved in the upgrade). Now the main table keeps becoming corrupt? In particular, the system insists that the indexes hav become corrupt.
>>>>>
>>>>>Could it be one machine, or even the way the new server has been configured?
>>>>>
>>>>>How does one go about finding what is causing the problem?
>>>>
>>>>It could be the configuration of Samba - check http://www.drouillard.biz/Tips&Tricks/Samba/Oplocks.htm