On-Line headache

Dear Netland: We changed over to On-Line 4.10 UG1 from SE 4.10 UD2 on our SCO Unix 3.2.4 486 Box. During the testing process everything worked great. We decided to "go live" with it this past weekend but unfortunately in the live environment (10 to 30 users), the save function of our FourGen Order Entry application kept bombing out with the following group of messages: SQL statement error number -240. Could not delete a row. SYSTEM error number -154. ISAM error: Deadlock Timeout Expired - Possible Deadlock. SQL statement error number -244. Could not do a physical-order read to fetch next row. SYSTEM error number -154. ISAM error: Deadlock Timeout Expired - Possible Deadlock. Is this a manifestation of the infamous twin paradox problem? We've increased the deadlock time out from 60 seconds to 300 seconds, but this error kept occurring. We have since gone back to SE but we'd sure like to go to On-Line for its much tauted features. Please note that the saving routines are extremely slow under SE, and under On-Line it just would not save orders once multiple users start using the software. Can someone shed some light on approaches we should take in avoiding/ overcoming this problem? Thanks in advance for any pointers.... Charles Lei Mediatech, Inc. Voice: (312) 828-9223 x.202 E-Mail: lei@mediatech.com UUCP: ..!uunet!mtcdev!lei