The crashes have never been properly diagnosed. The consist of indexing problems and problems with table updates(manually handling transactions). The current developer attributes the problem due to network problems. Too generic to work with. I'm sure that if I ran a sys(3054) that most of the queries are partially and non-optmized. The SQL Server was thrown at the problem. I don't use the term "kludgeware" lightly, the UI is peppered with search screens that consist of grid objects that consist of every record in a 30,000 record table. GULP!!!!! I could just imagine the network traffic. The prior high priced consulting team which consisted of a 13 year veteran to FoxPro/FoxBase said in his analysis quote: "The current system is so poorly engineered and implemented that only a complete re-write with an enterprise solution in mind would suffice". I concur with his opinion, a typical recipe for disaster the 80/20 rule in reverse 80%coding - 20%planning.