Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Transaction behavior
Message
From
07/12/2005 11:11:02
 
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Environment versions
Visual FoxPro:
VFP 9
OS:
Windows XP SP2
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01075467
Message ID:
01075753
Views:
29
Hi,

>Thanks a lot, Viv. Here is my colleague's logic: we process the stage tables and make changes in a bunch of our main operational related tables. Then we're saving all the changes made. We need to do that in the transaction because we can not have some tables saved changes and some don't. Since you confirmed the problem it means that we need to make sure to do imports when we don't have users in the system.

Surely it should be possible to keep the execution time of the code within the TRANSACTION.... END TRANSACTION to a reasonable limit. In your original post you showed the following code:
begin transaction
  llUpdate = tableupdate(.t.,.t.,"First Table")
  if not llUpdate
     rollback
     tablerevert all the changes done previously
     close the process && That logic is done in a separate method
  endif
  ...
end transaction
What happens in the 'close the process' method and the .... section that takes so long?

Regards,
Viv
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform