Hi,

1. Have you disabled disk write caching on the workstations. To disable write caching http://support.microsoft.com/default.aspx?scid=kb;en-us;324805

2. Are oplocks disabled. To disable see http://www.dataaccess.com/whitepapers/opportunlockingreadcaching.html

>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