<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><category>pcsoft.us.windev</category><copyright>Copyright 2026, PC SOFT</copyright><lastBuildDate>20 Jan 2015 15:44:00 Z</lastBuildDate><pubDate>19 Jan 2015 19:03:00 Z</pubDate><description>Hi,&#13;
&#13;
1) Start a transaction, with HTransactionStart&#13;
2) write some code to do HAdd (or HModify) on some files&#13;
3) Now before Canceling (or commiting) the transaction - do a ProgramEnd (or just break the execution with the help of the debugger).&#13;
Number (3) is just a common trick to emulate an unexpected application termination. It could be ANY abnormal termination ....&#13;
&#13;
Next time you go in the app, and try to run a query on the infected tables, you get an error saying you have a transaction that hasn't been canceled etc&#13;
You cannot cancel the transaction with code and you CANNOT cancel it even in the HF control center.&#13;
The only thing you can do is free the records to go on .....But the CC still shows this transaction in "transactions in progress".&#13;
&#13;
It does NOT happen when you use HF C/S v17.&#13;
It happens when using HF C/S v 19 (both with WD17 and WD19 applications)&#13;
&#13;
HF C/S v17, takes care of these kind of abnormal terminations - inside a transaction.&#13;
Just like the documentation says it does ...&#13;
&#13;
HF C/S v19 (latest) cannot handle this error anymore !!!!!&#13;
&#13;
Steven Sitas</description><ttl>30</ttl><generator>WEBDEV</generator><language>en_US</language><link>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/49938-major-bug-sql-v19/read.awp</link><title>MAJOR BUG in HF SQL v19</title><managingEditor>moderateur@pcsoft.fr (El moderador)</managingEditor><webMaster>webmaster@pcsoft.fr (El webmaster)</webMaster><item><author>guest</author><category>pcsoft.us.windev</category><comments>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/49938-major-bug-sql-v19-49963/read.awp</comments><pubDate>20 Jan 2015 15:44:00 Z</pubDate><description>Hi Steven,&#13;
&#13;
We too ran into quite uninteresting problems with transactions. (Unfortunately, the Free Tech Support was not able…</description><guid isPermaLink="true">https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/49938-major-bug-sql-v19-49963/read.awp</guid><link>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/49938-major-bug-sql-v19-49963/read.awp</link><source url="https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/49938-major-bug-sql-v19/read.awp">MAJOR BUG in HF SQL v19</source><title>Re: MAJOR BUG in HF SQL v19</title></item><item><author>guest</author><category>pcsoft.us.windev</category><comments>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/49938-major-bug-sql-v19-49939/read.awp</comments><pubDate>19 Jan 2015 19:16:00 Z</pubDate><description>Forgot to say:&#13;
The ONLY way to bypass this problem with HF SQL v19 is to RESTART HF SQL.&#13;
Then your HTransactionInterrupted() w…</description><guid isPermaLink="true">https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/49938-major-bug-sql-v19-49939/read.awp</guid><link>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/49938-major-bug-sql-v19-49939/read.awp</link><source url="https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/49938-major-bug-sql-v19/read.awp">MAJOR BUG in HF SQL v19</source><title>Re: MAJOR BUG in HF SQL v19</title></item></channel></rss>
