>For now then, we will disable write caching until we're able to create a new RAID Volume.
>
>Once we have the new RAID volume established, we will move the databases over to the new volume with write caching disabled and then re-enable write caching on the original volume.
>
>Does that sound like a ligitimate solution?
Nope.
The issue is not RAID. The issue is the write cache. Don't use it. Period. This is not a FoxPro issue, but a database issue. Most database applications will have problems with write caching.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer