>OK. I need help. My experience with NT Server is better than it was last week, and a LOT better than 6 months ago, but not nearly good enough in my opinion. Anyway, I'm trying to prevent someone from unnecessarily bashing VFP and I don't have the tools to do it.
>
>We recently migrated from Novell 3.12 to NT 4.0. Now all the FoxPro apps are running slower than other apps. (FPD, FPW and VFP) This morning, immediately after rebuilding the indexes on the main VFP app, the NT server crashed when people began logging into the app. The DBC caused the crash, but I'm not sure how.
>
>I'm hearing that somehow FoxPro conflicts with RAID and that the ONLY (??!!) solution is to move to a C/S application. The fault is being blamed on FoxPro's inablility to be directed at specific network devices (I'm not sure if I'm saying that properly.)
>
>The DBC that crashed the server is a very small app. The main tables are about 75,000 and 60,000 records each and it's being used by about 6 users processing an average of about 1 transaction/each per minute.
>Worst case scenario, 4 or 5 of them might try to update/add records at once. THIS IS NOT A HEAVY DUTY APP!
>
>There are some minor design flaws that I've already been investigating, but on the whole, it works great. And I know it can't only be the application design because other FP apps are getting hit as well.
>
>Can someone bring me up to speed, or tell me where to go to find out about FP *conflicts* with RAID and what pitfalls to look out for in terms of where shared databases should be stored, how NT should be configured to optimize FP and any other obstacles I should be looking for?
>
>TIA


Fox in no way conflicts with RAID. However, you should make sure ALL write cache is turned off. This is not a Fox problem, but is a good rule for all database systems.