What the application is doing is building an appointmentcalendar with preconfigured time slots and writing the appointment records outto the database. The application is using the Infragistics WinSchedulecontrols. Each appointment record can be up to 2600 bytes (the calendarcontrols require a 2048 variable binary field) in addition to the other fieldsin the record and there can be anywhere from a couple of hundred records tothousands depending on the time period that the calendar covers. In one of thetests I ran there were around 600 records. When I ran the save using ES withouta transaction it completed in a couple of seconds. When I ran it on atransaction it failed at around 35 seconds. In general it’s the larger numberof records where I see the problem, but it’s not consistent.

I’m getting a random error when saving via the Enterpriseserver. I have a form with 5 business objects and there are parent childrelationships. I’m saving these objects using the form save method on a transactionand every so often the transaction fails (see attached screen shot). If Iremove the transaction and simply save by form, it works 100% of the time. If Ibypass the Enterprise server and use a direct connection, both save by formwith and without a transaction works 100% of the time. There is something aboutsaving on a transaction via the Enterprise server that is randomly failing. TheSQL box is the same system for both the direct and Enterprise connections andthe number of pools is set to the default of 100. And suggestions?