Micheal and John:

First of all, thanks for the quick response.

The way I ran into this problem was having my VFP application call an sp on SQL Server (7.0 Beta 3, I left that out of the original e-mail). The sp code contains a BEGIN/COMMIT transaction (it's a simple sp that pops a number from a table - a UID farm, if you will). It's not isolated to this sp, however, since I'm getting similar results w/ any DML commands. What's unusual is this:

1. It hasn't always done this.
2. My partner who is connected to the same server can execute the commands w/o incident.

These strongly suggest that it's my machine although I've not change any settings, etc. on my machine. I'm running VFP 6.0 (no Service Packs installed) and hitting SQL 7.0 (Beta 3).

Thanks again.