In my VFP 6.0 code accessing SQL 6.5 backend data, I have an explicit "BEGIN TRANSACTION" to start my all-or-nothing update process. This particular transaction consists of approximately 7500 record updates and 8000 record inserts. When I first tested the code, the transaction log size was at 75 mb with only half of the process done when the log is filled up. I have since expanded it up to as much as 1250 mb and the log seems to fill up before the process gets a chance to complete (about 85% of process done). Is there something else that I could do in lieu of upsizing the log file? Or am I unintentionally doing something else that might have filled up the log that quickly?

Please help. Thanks.