Hi Ben,
It has been a very long time since I used it but it seemed to work fine when I did use it. It might have been during version 4.x. Unfortunately, I found it EXTREMELY slow. It was much, much faster to enter the data into a temporary or batch table and then when the user was ready to commit, copy it to the real table. If they wanted to roll back then I just deleted the data from the temporary table. I think you will find that most of the people on this list came to the same conclusions.
Best regards,
Mike Young
--Original Message Text---
From: Ben Strickland
Date: Wed, 1 Aug 2001 22:01:52 -0700
Hello,
I have a situation with 6.5 where I am using the Transaction On/Off feature and each time I execute a set of commands and then Rollback it damages the database. I know the database is fine before running this routine because I checked the database. It appears that the database is fine after the Commit command.
Is there anything usual with the Transaction On/Off, Commit and Rollback options? Would appreciate help or your experience encountered with these commands.
Ben
- Using Trans on/Commit/Rollback Ben Strickland
- Michael Young
