Re: [firebird-support] Insert SQL Deadlock Issue

2017-01-04 Thread Vishal Tiwari vishuals...@yahoo.co.in [firebird-support]
Got it from here: http://api.256file.com/fbclient.dll/en-download-67763.html On Thursday, 5 January 2017 9:40 AM, "Vishal Tiwari vishuals...@yahoo.co.in [firebird-support]" wrote:   @WBR: Are you saying, the fbclient.dll and (gds32.dll) are

Re: [firebird-support] Insert SQL Deadlock Issue

2017-01-04 Thread Vishal Tiwari vishuals...@yahoo.co.in [firebird-support]
@WBR: Are you saying, the fbclient.dll and (gds32.dll) are belonging to older version than the current firebird version? If yes, then would you please tell, how shall I get them? by reinstalling FIrebird, or is there any link by which I could download them? Thanks. On Thursday, 5 January

Re: [firebird-support] Insert SQL Deadlock Issue

2017-01-04 Thread Vishal Tiwari vishuals...@yahoo.co.in [firebird-support]
Any other way? On Wednesday, 4 January 2017 6:11 PM, "Dimitry Sibiryakov s...@ibphoenix.com [firebird-support]" wrote: 04.01.2017 13:36, Vishal Tiwari vishuals...@yahoo.co.in [firebird-support] wrote: > Error 3: > *validation error for column VAT,

Re: [firebird-support] Insert SQL Deadlock Issue

2017-01-04 Thread Dimitry Sibiryakov s...@ibphoenix.com [firebird-support]
04.01.2017 13:36, Vishal Tiwari vishuals...@yahoo.co.in [firebird-support] wrote: > Error 3: > *validation error for column VAT, value "*** null ***"* > *-sql_dialect set database dialect n* > * > * First of all fix fbclient.dll(gds32.dll) - firebird.msg version

Re: [firebird-support] Insert SQL Deadlock Issue

2017-01-04 Thread Vishal Tiwari vishuals...@yahoo.co.in [firebird-support]
Just checked in the code Transaction components are used. Sorry for mistake. On Wednesday, 4 January 2017 5:40 PM, "Vishal Tiwari vishuals...@yahoo.co.in [firebird-support]" wrote:   Hi All,  At production department, we are receiving below errors,

[firebird-support] Insert SQL Deadlock Issue

2017-01-04 Thread Vishal Tiwari vishuals...@yahoo.co.in [firebird-support]
Hi All,  At production department, we are receiving below errors, not for all times, but frequently. We tried looking into code and found that there is a very simple insert statement which might cause that issue. Because functionality executes that Insert statement.  Wondering how to resolve