*snip*
>Troubleshooting steps taken so far:
>1. I created an automated version of this form which does the exact same operations as a people-driven version
>
>2. Set up the test form to run on 2 workstations. When 1 user is running, utilization is almost zero, adding the second instance (separate wrkstation) shoots utilization to 80-90%
>
>3. Tried changing from pessimistic to optimistic row buffering. No measurable effect.
>
>4. changed the record creation from append blank with replace, to insert-sql style, no effect.
>
>5. Zapped the child table, has a huge effect, but this is not a viable solution. Selectively deleting some historical data helps also, but only so much. The table has about 175k records in its unmodified form.
>
>6. Commented out the actual record creation and save - drops utilization to 0.

---

Jim, buffering only relates to updating exisitng records, not the addition of new records. The only thing that I can think might be contributing to your system load is if your child table has an enormous structure combined with an enormous number of indexes. Can you post a DISPLAY STRUCTURE?