>After moving to a new server installation, we have been having "delayed write errors" off an on. Seems to be when we have heavy usage. Before the switch, all workstations had a mapped drive to the database location on the server. After the move to the new server all workstations located the database location using UNC.
>
>Our guess is that with the UNC naming convention, there is a delay in opening the Databases for usage and when heavy usage, this would be causing a problem and throwing the "delayed write error". We changed the datalocation to mapped drives and it seems to have solved the problem.
>
>The number of workstations are not that great. Approx. 25
>
>I an not comfortable that this is really solving our issue, however, it seems to have corrected the problem with mappings.
>
>Has anyone experienced problems like this?
>
>Thanks in advance

Very odd that it would work ok with mapping the drive and not UNC - if anything I would think it would be the opposite.
Anyway might take a look at your anti-virus software - I've had that cause me network issues with VFP in the past...