Zoran Bonuš

Yes, official installer is the safest method for client-only install. It is also well documented in the FB3 Quick Start Guide, chapter 3.5, and in /doc/ folder in the installation path (e.g. "c:\Program Files\Firebird\Firebird_3_0\doc") For manual installation, copying fbclient.dll / gds32.dll + msvcp100.dll + msvcr100.dll + firebird.msg works fine too. I just want to add that there is also a handy community-mantained chocolatey.org package - can silently install (and upgrade) server or client-only choco install firebird /ClientOnly (you need to install chocolatey first, of course).

Flamerobin www.flamerobin.org (free, opensource) Database Workbench www.upscene.com (paid) IBExpert ibexpert.net (paid)

scrcpy https://github.com/Genymobile/scrcpy opensource, nothing to install on the phone - just enable usb debugging and setup adb over tcpip

You may check https://www.embarcadero.com/rad-in-action/migration-upgrade-center

Winsoft Comport ($80) https://winsoft.sk/comport.htm

No issues here neither....running 1909 for 6 months on several machines.

Exactly, just what I was about to recommend. You create deadlock because the new value of VIEW_COUNT depends on the old value, and due to the nature of multi-generation architecture a simultaneous transactions, there can be different old values, depending on the isolation settings of your transaction. Using generator/sequence for view_count circumvalents the problem for this specific update query. However, a proper transaction setting is preferred anyway. There is no magic solve-it-all setting, I recommend studing the docs too .. will most likely came in handy later anyway.

Just a heads up: if you you are using IBX (IBExpress) library. There is a annoying regression in current 10.3.3 release. Already reported here: https://quality.embarcadero.com/browse/RSP-26997 When you use IBStoredProcedure + prepare/refresh string input params (in design/IDE or at runtime), you get an exception or silent corruption. I have just learnt about it today, crashing our system in production. Patch is available in the bug report.

Double check the Accept and Accept-* headers of your request: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/406