Re: [firebird-support] Engine12 32 64 bit question
How to know which fbclient.dll is 32bit and which one is 64bit? By the file size? Thank you. On Fri, May 17, 2019 at 7:42 PM Helen Borrie hele...@tpg.com.au [firebird-support] wrote: > > > a...@liberov.net wrote: > > > I'm developing a 32 bit application running on 64 bit Windows with 64 > bit Firebird 3 server. > > > I use 32 bit library to connect to Firebird > > > C:\Program Files\Firebird\Firebird_3_0\WOW64\fbclient.dll > > > I'm getting the engine12 Win32 error 193. This means some bitness > > mismatch. The message lists what seems to be a 64 bit dll. > > > Are there any settings to specify to enable such a connection? > > No - such a connection is totally allowed already, no special > configuration required. The server does not know (nor care) whether > the client is 32 or 64-bit. > > > There are other 64 bit applications using the server, but this > application has to be 32 bit. > > Somehow, Windows is finding the wrong client version, via some PATH > setting, which presumably your 64-bit clients are finding correctly. > > Place a copy of the 32-bit fbclient.dll in the same directory where the > client application executable is located, to ensure that Windows will > find it first and not seek it out via the PATH variable. > > Helen > > --- > This email has been checked for viruses by AVG. > https://www.avg.com > > >
Re: [firebird-support] Engine12 32 64 bit question
a...@liberov.net wrote: > I'm developing a 32 bit application running on 64 bit Windows with 64 bit > Firebird 3 server. > I use 32 bit library to connect to Firebird > C:\Program Files\Firebird\Firebird_3_0\WOW64\fbclient.dll > I'm getting the engine12 Win32 error 193. This means some bitness > mismatch. The message lists what seems to be a 64 bit dll. > Are there any settings to specify to enable such a connection? No - such a connection is totally allowed already, no special configuration required. The server does not know (nor care) whether the client is 32 or 64-bit. > There are other 64 bit applications using the server, but this application > has to be 32 bit. Somehow, Windows is finding the wrong client version, via some PATH setting, which presumably your 64-bit clients are finding correctly. Place a copy of the 32-bit fbclient.dll in the same directory where the client application executable is located, to ensure that Windows will find it first and not seek it out via the PATH variable. Helen --- This email has been checked for viruses by AVG. https://www.avg.com
[firebird-support] Engine12 32 64 bit question
Hi, I'm developing a 32 bit application running on 64 bit Windows with 64 bit Firebird 3 server. I use 32 bit library to connect to Firebird C:\Program Files\Firebird\Firebird_3_0\WOW64\fbclient.dll I'm getting the engine12 Win32 error 193. This means some bitness mismatch. The message lists what seems to be a 64 bit dll. Are there any settings to specify to enable such a connection? There are other 64 bit applications using the server, but this application has to be 32 bit. Thanks in advance.
[firebird-support] FB 2.1 transaction question
Sometimes our application works from remote place via VPN over wireless Internet connection. Often connections brakes and we have active DB connections in MON$ATTACHMENTS for a long time and their TA's blocks further work. Is this same case as in your reply? At least we receive an errors in 'unique' indexes - we use artificial counters in special table to generate sequential document numbers for each employee. So, when employee reconnect to continue his work - he can't create new document: TA, who was increase this counter, was broken and was not committed, so new document watch an old counter, and gets an already used next counter value. But previous document in broken TA, that uses his next counter value, was inserted in respective table and his number is already in unique index (but invisible for new TA's). This belongs not only for counters. E.g., we create a customer with unique short name, and when we reconnect after connection lose - we can't re-create customer with this short name, until broken connection will closed. Firebird version: 2.5.8. For such extremal cases your application can present for SYSDBA special window that shows table with data from MON$ATTACHMENTS (login, connection's start date, client IP, app name). Deleting record from MON$ATTACHMENTS will close connection, so you can continue. Again, only necessary in the case where the connection remains active while the transaction is stalled. _._,___
