Dmitry Arefiev

Is it bad to use official DLL ? Several questions: * are you limited in distributing capabilities of this DLL (license, space, what ever) ? * who will support you, when something is broken, and you are using non-official connectivity ? * with whom you you can discuss your connectivity problems on INet, if you are using some from 3d party ? * how long will live your software, when 3d party provider is out of business, and DLL "insides"/protocol are changed ?

This is IProviderSupport or IProviderSupportNG.

Yes, it is.

This issue was (most probably) fixed in 10.2.2. Your workaround is almost correct.

You can do, when both conditions are met: * TOracleDataSet and TgQuery both are inherited from TDataSet * and properly implement IProviderSupport methods: procedure Form1.Proc1( aQry : TDataSet ); begin ... aQry.Close; (aQry as IProviderSupport).PSSetCommandText('select * from xyz'); aQry.Open; ... end;

Could you please provide some tickets to better understand what and where.

https://www.wireshark.org/ https://www.telerik.com/fiddler

In this case I would try to capture HTTP packets sent from 10.1.2 and 10.2.1 clients. And will try to understand what is the difference between them, which may lead to this failure ...

This is not related to REST client. But is related to REST server, which is accessing to InterBase server. And due to some reason the database specified in FireDAC connection parameters is not available. Start from checking your InterBase interbase.log ...

The patch and instruction is published there: https://quality.embarcadero.com/browse/RSP-23656

@RDPasqua, depends on RAD Studio version. In 10.3 standard JSON library is much faster and reliable.

This issue is fixed in 10.3 Rio. And more is comming in Updates. If to stay with 10.1, then search and install IDE HotFix Pack.

GetValue (@Rec)

https://quality.embarcadero.com/browse/RSP-20857 Will be fixed in 10.3 Update 1

https://quality.embarcadero.com/browse/RSP-20349